joepie91
/
pegjs
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
redux
master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '9956b42392'
${ noResults }
pegjs/package.json

70 lines
1.8 KiB
JSON
Raw Normal View History Unescape Escape

Add package.json for installing as Node package
14 years ago
{
package.json: Reformat to formatting used by npm This makes it possible to do e.g. "npm install --save" without a lot of whitespace noise in the resulting diff.
9 years ago
"name": "pegjs",
Update version to 0.10.0
8 years ago
"version": "0.10.0",
package.json: Reformat to formatting used by npm This makes it possible to do e.g. "npm install --save" without a lot of whitespace noise in the resulting diff.
9 years ago
"description": "Parser generator for JavaScript",
"keywords": [
"parser generator",
"PEG"
],
"homepage": "http://pegjs.org/",
"bugs": "https://github.com/pegjs/pegjs/issues",
"license": "MIT",
"author": "David Majda <david@majda.cz> (http://majda.cz/)",
Git repo npmization: Make the repo a npm package Includes: * Moving the source code from /src to /lib. * Adding an explicit file list to package.json * Updating the Makefile. * Updating the spec and benchmark suites and their READMEs. Part of a fix for GH-32.
12 years ago
"files": [
Convert CHANGELOG to Markdown * Convert CHANGELOG to Markdown. * Improve formatting a bit. * Add links to GitHub issues * Fix typos.
11 years ago
"CHANGELOG.md",
Git repo npmization: Make the repo a npm package Includes: * Moving the source code from /src to /lib. * Adding an explicit file list to package.json * Updating the Makefile. * Updating the spec and benchmark suites and their READMEs. Part of a fix for GH-32.
12 years ago
"LICENSE",
"README.md",
"VERSION",
"bin/pegjs",
"examples/arithmetics.pegjs",
"examples/css.pegjs",
"examples/javascript.pegjs",
"examples/json.pegjs",
Utility functions cleanup: Split lib/utils.js Split lib/utils.js into multiple files. Some of the functions were generic, these were moved into files in lib/utils. Other funtions were specific for the compiler, these were moved to files in lib/compiler. This commit only moves functions around -- there is no renaming and cleanup performed. Both will come later.
11 years ago
"lib/compiler/asts.js",
Move lib/compiler.js to lib/compiler/index.js This makes "compiler" a regular Node.js module.
9 years ago
"lib/compiler/index.js",
Rename javascript.js to js.js Short & sweet.
9 years ago
"lib/compiler/js.js",
Code generator rewrite This is a complete rewrite of the PEG.js code generator. Its goals are: 1. Allow optimizing the generated parser code for code size as well as for parsing speed. 2. Prepare ground for future optimizations and big features (like incremental parsing). 2. Replace the old template-based code-generation system with something more lightweight and flexible. 4. General code cleanup (structure, style, variable names, ...). New Architecture ---------------- The new code generator consists of two steps: * Bytecode generator -- produces bytecode for an abstract virtual machine * JavaScript generator -- produces JavaScript code based on the bytecode The abstract virtual machine is stack-based. Originally I wanted to make it register-based, but it turned out that all the code related to it would be more complex and the bytecode itself would be longer (because of explicit register specifications in instructions). The only downsides of the stack-based approach seem to be few small inefficiencies (see e.g. the |NIP| instruction), which seem to be insignificant. The new generator allows optimizing for parsing speed or code size (you can choose using the |optimize| option of the |PEG.buildParser| method or the --optimize/-o option on the command-line). When optimizing for size, the JavaScript generator emits the bytecode together with its constant table and a generic bytecode interpreter. Because the interpreter is small and the bytecode and constant table grow only slowly with size of the grammar, the resulting parser is also small. When optimizing for speed, the JavaScript generator just compiles the bytecode into JavaScript. The generated code is relatively efficient, so the resulting parser is fast. Internal Identifiers -------------------- As a small bonus, all internal identifiers visible to user code in the initializer, actions and predicates are prefixed by |peg$|. This lowers the chance that identifiers in user code will conflict with the ones from PEG.js. It also makes using any internals in user code ugly, which is a good thing. This solves GH-92. Performance ----------- The new code generator improved parsing speed and parser code size significantly. The generated parsers are now: * 39% faster when optimizing for speed * 69% smaller when optimizing for size (without minification) * 31% smaller when optimizing for size (with minification) (Parsing speed was measured using the |benchmark/run| script. Code size was measured by generating parsers for examples in the |examples| directory and adding up the file sizes. Minification was done by |uglify --ascii| in version 1.3.4.) Final Note ---------- This is just a beginning! The new code generator lays a foundation upon which many optimizations and improvements can (and will) be made. Stay tuned :-)
12 years ago
"lib/compiler/opcodes.js",
"lib/compiler/passes/generate-bytecode.js",
Rename generate-javascript.js to generate-js.js Short & sweet.
9 years ago
"lib/compiler/passes/generate-js.js",
Git repo npmization: Make the repo a npm package Includes: * Moving the source code from /src to /lib. * Adding an explicit file list to package.json * Updating the Makefile. * Updating the spec and benchmark suites and their READMEs. Part of a fix for GH-32.
12 years ago
"lib/compiler/passes/remove-proxy-rules.js",
Report duplicate labels as errors Resolves #270.
8 years ago
"lib/compiler/passes/report-duplicate-labels.js",
package.json: Sort files alphabetically
8 years ago
"lib/compiler/passes/report-duplicate-rules.js",
Align names of compiler passes that detect infinite loops Rename compiler passes as follows: reportLeftRecursion -> reportInfiniteRecursion reportInfiniteLoops -> reportInfiniteRepetition This reflects the fact that both passes detect different ways of causing the same problem (possible infinite loop when parsing).
8 years ago
"lib/compiler/passes/report-infinite-recursion.js",
package.json: Sort files alphabetically
8 years ago
"lib/compiler/passes/report-infinite-repetition.js",
Talk about "undefined rules" instead of "missing rules" internally The new terminology is more precise and in line with commonly used programming languages. The change involves mainly renaming related compiler pass and files associated with it.
8 years ago
"lib/compiler/passes/report-undefined-rules.js",
package.json: Sort files alphabetically
8 years ago
"lib/compiler/visitor.js",
Git repo npmization: Make the repo a npm package Includes: * Moving the source code from /src to /lib. * Adding an explicit file list to package.json * Updating the Makefile. * Updating the spec and benchmark suites and their READMEs. Part of a fix for GH-32.
12 years ago
"lib/grammar-error.js",
"lib/parser.js",
"lib/peg.js",
"package.json"
],
package.json: Reformat to formatting used by npm This makes it possible to do e.g. "npm install --save" without a lot of whitespace noise in the resulting diff.
9 years ago
"main": "lib/peg",
"bin": "bin/pegjs",
"repository": "pegjs/pegjs",
"scripts": {
Switch from Make to Gulp The core of the transition is getting rid of Makefile and replacing it with gulpfile.js. The rest is details (fixing dependencies, changing all references to "make", etc.). Target/task names mostly stay the same, so in most cases "gulp foo" does what "make foo" did before. The only exceptions are "make browser" and "make browserclean", which are now "gulp browser:build" and "gulp browser:clean" (it feels more systematic). Functionality is mostly unchanged (modulo Gulp clutter in the console), but there are two small exceptions: gulp spec The reporter now displays just dots while previously it displayed spec descriptions. There is also a deprecation warning (most likely because I used an old version of gulp-jasmine in order to support Jasmine 1.x). I kept these issues unfixed because I plan to switch to Mocha soon (#409). gulp browser:build The copyright header is now added manually both to the development and minified build. Before, it was added only to the development build and the minified build relied on preserving it using "uglify --comments". This was broken since switching to //-style comments. There is now also an empty line between the header and the source code. Fixes #444.
8 years ago
"test": "gulp"
Make "npm test" work This is will be useful for Travis CI integration
12 years ago
},
Clean up package.json The engine's and dependencies' versions are the ones I've tested with. Lower version will probably work too, but I don't want to spend more time testing now so I'll play it safe.
14 years ago
"devDependencies": {
Pass the browser version through Babel This will allow to use ES2015 constructs in PEG.js code. See #442.
8 years ago
"babel-preset-es2015": "6.14.0",
"babelify": "7.3.0",
Use browserify 13.1.0
8 years ago
"browserify": "13.1.0",
Switch from Make to Gulp The core of the transition is getting rid of Makefile and replacing it with gulpfile.js. The rest is details (fixing dependencies, changing all references to "make", etc.). Target/task names mostly stay the same, so in most cases "gulp foo" does what "make foo" did before. The only exceptions are "make browser" and "make browserclean", which are now "gulp browser:build" and "gulp browser:clean" (it feels more systematic). Functionality is mostly unchanged (modulo Gulp clutter in the console), but there are two small exceptions: gulp spec The reporter now displays just dots while previously it displayed spec descriptions. There is also a deprecation warning (most likely because I used an old version of gulp-jasmine in order to support Jasmine 1.x). I kept these issues unfixed because I plan to switch to Mocha soon (#409). gulp browser:build The copyright header is now added manually both to the development and minified build. Before, it was added only to the development build and the minified build relied on preserving it using "uglify --comments". This was broken since switching to //-style comments. There is now also an empty line between the header and the source code. Fixes #444.
8 years ago
"del": "2.2.2",
Code style: Use eslint-config-dmajda ESLint configuration This change leads to quite some errors being reported by ESLint. These will be fixed in subsequent commits. Part of #407.
8 years ago
"eslint-config-dmajda": "1.0.0",
package.json: Add packages that will be needed soon Add "express" and "morgan" packages, which will be needed by soon-to-be-introduced spec server and benchmark server. See #442.
8 years ago
"express": "4.14.0",
Add `glob` dev dependency used in spec and benchmark servers
8 years ago
"glob": "7.0.6",
Switch from Make to Gulp The core of the transition is getting rid of Makefile and replacing it with gulpfile.js. The rest is details (fixing dependencies, changing all references to "make", etc.). Target/task names mostly stay the same, so in most cases "gulp foo" does what "make foo" did before. The only exceptions are "make browser" and "make browserclean", which are now "gulp browser:build" and "gulp browser:clean" (it feels more systematic). Functionality is mostly unchanged (modulo Gulp clutter in the console), but there are two small exceptions: gulp spec The reporter now displays just dots while previously it displayed spec descriptions. There is also a deprecation warning (most likely because I used an old version of gulp-jasmine in order to support Jasmine 1.x). I kept these issues unfixed because I plan to switch to Mocha soon (#409). gulp browser:build The copyright header is now added manually both to the development and minified build. Before, it was added only to the development build and the minified build relied on preserving it using "uglify --comments". This was broken since switching to //-style comments. There is now also an empty line between the header and the source code. Fixes #444.
8 years ago
"gulp": "3.9.1",
"gulp-eslint": "3.0.1",
"gulp-header": "1.8.8",
"gulp-jasmine": "0.2.0",
"gulp-rename": "1.2.2",
"gulp-transform": "1.0.8",
"gulp-uglify": "2.0.0",
package.json: Add packages that will be needed soon Add "express" and "morgan" packages, which will be needed by soon-to-be-introduced spec server and benchmark server. See #442.
8 years ago
"morgan": "1.7.0",
Switch from Make to Gulp The core of the transition is getting rid of Makefile and replacing it with gulpfile.js. The rest is details (fixing dependencies, changing all references to "make", etc.). Target/task names mostly stay the same, so in most cases "gulp foo" does what "make foo" did before. The only exceptions are "make browser" and "make browserclean", which are now "gulp browser:build" and "gulp browser:clean" (it feels more systematic). Functionality is mostly unchanged (modulo Gulp clutter in the console), but there are two small exceptions: gulp spec The reporter now displays just dots while previously it displayed spec descriptions. There is also a deprecation warning (most likely because I used an old version of gulp-jasmine in order to support Jasmine 1.x). I kept these issues unfixed because I plan to switch to Mocha soon (#409). gulp browser:build The copyright header is now added manually both to the development and minified build. Before, it was added only to the development build and the minified build relied on preserving it using "uglify --comments". This was broken since switching to //-style comments. There is now also an empty line between the header and the source code. Fixes #444.
8 years ago
"vinyl-buffer": "1.0.0",
"vinyl-source-stream": "1.1.0"
Clean up package.json The engine's and dependencies' versions are the ones I've tested with. Lower version will probably work too, but I don't want to spend more time testing now so I'll play it safe.
14 years ago
},
package.json: Reformat to formatting used by npm This makes it possible to do e.g. "npm install --save" without a lot of whitespace noise in the resulting diff.
9 years ago
"engines": {
Drop Node 0.10.x & 0.12.x support See #442.
8 years ago
"node": ">=4"
Add package.json for installing as Node package
14 years ago
}
}