Make PEG.js's Git repository a valid npm pacakge

[dmajda]

PEG.js's Git repository should be a valid npm pacakge, so that development versions can be installed more easily using just the following commands:

git clone git://github.com/dmajda/pegjs.git
npm install ./pegjs

Right now attempt to run these commands ends up with npm error:

npm ERR! Could not install: ./pegjs/
npm ERR! Error: Invalid version: @VERSION
npm ERR! Must be X.Y.Z, with an optional trailing tag.
npm ERR! See the section on 'version' in `npm help json`
npm ERR!     at /usr/local/lib/node_modules/npm/lib/utils/read-json.js:257:13
npm ERR!     at /usr/local/lib/node_modules/npm/lib/utils/read-json.js:132:32
npm ERR!     at P (/usr/local/lib/node_modules/npm/lib/utils/read-json.js:109:40)
npm ERR!     at cb (/usr/local/lib/node_modules/npm/lib/utils/graceful-fs.js:31:9)
npm ERR!     at [object Object].<anonymous> (fs.js:107:5)
npm ERR!     at [object Object].emit (events.js:61:17)
npm ERR!     at afterRead (fs.js:878:12)
npm ERR!     at wrapper (fs.js:245:17)
npm ERR! Report this *entire* log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>
npm ERR! 
npm ERR! System Linux 2.6.38-10-generic
npm ERR! command "node" "/usr/local/bin/npm" "install" "./pegjs/"
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /home/dmajda/tmp/npm-debug.log
npm not ok

Two things will need to happen to resolve this issue:

1. The build system needs to avoid concatenating files into one. We should just use require in Node.js environment. For browser environment, the files will still need to be assembled into one, but this is probably doable using Browserify or some similar tool.
2. The @VERSION substitution should be eliminated at least from the pacakge.json file. This will lead to small duplication of the current version value, but this is lesser evil than making installation of PEG.js development versions easier.

[dmajda]

Apparently Browserify works differently than I thought, so I'd need another tool or write something myself. Moving to post-1.0 milestone, but I'll accept patches for this anytime.

My idea in general is that PEG.js would be a collection of regular Node.js modules (each file in src would become a module) which will be required as needed. Then there would be a script/tool that would process the source code, figure out the dependencies and basically inline them, thus building a browser version. It may also require that the modules have somewhat restricted format (e.g. exactly one assignment to module.exports) because they would probably need to be changed somewhat when inlining.

The tricky point here is avoiding duplication when some module would be required from multiple places. This would be a case with utils.js for example. I still didn't figure out how to do this without introducing boilerplate code.

[dmajda]

This is fixed now, closing.