pegjs/spec/.eslintrc.json

{
  "env": {
    "commonjs": true,
    "jasmine": true
  }
}
ESLint: Set environments better Instead of setting ESLint environment to "node" globally, set it on per-directory basis using separate .eslintrc.json files: Directory Environment ----------------------- bin node lib commonjs spec jasmine It was impossible to use this approach for the "benchmark" directory which contains a mix of files used in various environments. For benchmark/run, the environment is set inline. For the other files, as well as spec/helpers.js, the globals are declared manually (it is impossible to express how these files are used just by a list of environments). Fixes #408. 9 years ago			`{`
			`"env": {`
Pass spec code through Babel before serving it to the browser This will allow to use ES2015 constructs in spec code. The change required introducing a small server, which serves both PEG.js and spec code passed through Babel and bundled together. This allowed to convert the specs to regular modules and get rid of the hackery that was previously needed to make them run both in Node.js and in the browser. Note the specs no longer exercise the browser version. This will allow to spec PEG.js internals in the future. See #442. 8 years ago			`"commonjs": true,`
ESLint: Set environments better Instead of setting ESLint environment to "node" globally, set it on per-directory basis using separate .eslintrc.json files: Directory Environment ----------------------- bin node lib commonjs spec jasmine It was impossible to use this approach for the "benchmark" directory which contains a mix of files used in various environments. For benchmark/run, the environment is set inline. For the other files, as well as spec/helpers.js, the globals are declared manually (it is impossible to express how these files are used just by a list of environments). Fixes #408. 9 years ago			`"jasmine": true`
			`}`
			`}`