joepie91/pegjs
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
pegjs/spec
History
David Majda 810567d865 UMD parsers: Allow specifying parser dependencies 
Introduce two ways of specifying parser dependencies: the "dependencies"
option of PEG.buildParser and the -d/--dependency CLI option. Specified
dependencies are translated into AMD dependencies and Node.js's
"require" calls when generating an UMD parser.

Part of work on #362.
2016-05-03 11:50:01 +02:00
..
api UMD parsers: Allow specifying parser dependencies 2016-05-03 11:50:01 +02:00
behavior Support passing custom location info to "error" and "expected" 2016-04-27 14:11:32 +02:00
unit Rewrite handling of optional parameters 2016-04-27 13:40:23 +02:00
vendor/jasmine
.eslintrc.json ESLint: Set environments better 2016-01-29 14:50:38 +01:00
helpers.js ESLint: Set environments better 2016-01-29 14:50:38 +01:00
index.html Update version to 0.9.0 2015-08-30 08:22:26 +02:00
README.md Use sentence case consistently in {spec,benchmark}/README.md headers 2014-05-10 16:40:39 +02:00

README.md

PEG.js Spec Suite

This is the PEG.js spec suite. It ensures PEG.js works correctly. All specs should always pass on all supported platforms.

Running in Node.js

All commands in the following steps need to be executed in PEG.js root directory (one level up from this one).

  1. Install all PEG.js dependencies, including development ones:

    $ npm install

  2. Execute the spec suite:

    $ make spec

  3. Watch the specs pass (or fail).

Running in the Browser

All commands in the following steps need to be executed in PEG.js root directory (one level up from this one).

  1. Make sure you have Node.js and Python installed.

  2. Install all PEG.js dependencies, including development ones:

    $ npm install

  3. Build browser version of PEG.js:

    $ make browser

  4. Serve PEG.js root directory using a web server:

    $ python -m SimpleHTTPServer

  5. Point your browser to the spec suite.

  6. Watch the specs pass (or fail).