joepie91/pegjs
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
pegjs/spec
History
David Majda c134e06229 Move "use strict" directives up 
Move "use strict" directives to the first line of each file. In
particular, move them above any ESLint comments, which are far less
important.

There are few exceptions:

  Executable files

    In these, the "use strict" directive must give way to the shebang.

  lib/parser.js

    Here, the "Generated by..." comment comes first. Also, ESLint
    comments are prepended in post-processing.
2016-09-22 16:43:42 +02:00
..
api Move "use strict" directives up 2016-09-22 16:43:42 +02:00
behavior Move "use strict" directives up 2016-09-22 16:43:42 +02:00
unit Avoid aligning "=" 2016-09-22 09:56:29 +02:00
vendor/jasmine Upgrade jasmine and jasmine-node 2013-08-22 09:07:19 +02:00
.eslintrc.json Pass spec code through Babel before serving it to the browser 2016-09-08 14:53:00 +02:00
index.html Avoid aligning "=" 2016-09-22 09:56:29 +02:00
README.md Pass spec code through Babel before serving it to the browser 2016-09-08 14:53:00 +02:00
server Move "use strict" directives up 2016-09-22 16:43:42 +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 installed.

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

    $ npm install

  3. Serve the spec suite using a web server:

    $ spec/server

  4. Point your browser to the spec suite.

  5. Watch the specs pass (or fail).