Closed nolanlawson closed 8 years ago
I'd assume that's from a comment somewhere weird but wasn't able to find it On Sep 12, 2014 5:51 AM, "Nolan Lawson" notifications@github.com wrote:
wtf?
pouchdb-replication-stream@0.1.0 dev /Users/nolan/workspace/pouchdb-replication-stream browserify test/test.js > test/test-bundle.js && npm run dev-server
/Users/nolan/workspace/pouchdb-replication-stream/node_modules/es3ify/node_modules/jstransform/src/jstransform.js:222 throw e; ^ Error: Parse Error: Line 2: Unexpected token : at throwError (/Users/nolan/workspace/pouchdb-replication-stream/node_modules/es3ify/node_modules/esprima-fb/esprima.js:2154:21) at throwUnexpected (/Users/nolan/workspace/pouchdb-replication-stream/node_modules/es3ify/node_modules/esprima-fb/esprima.js:2216:9) at consumeSemicolon (/Users/nolan/workspace/pouchdb-replication-stream/node_modules/es3ify/node_modules/esprima-fb/esprima.js:2302:13) at parseStatement (/Users/nolan/workspace/pouchdb-replication-stream/node_modules/es3ify/node_modules/esprima-fb/esprima.js:4150:9) at /Users/nolan/workspace/pouchdb-replication-stream/node_modules/es3ify/node_modules/esprima-fb/esprima.js:5832:38 at parseSourceElement (/Users/nolan/workspace/pouchdb-replication-stream/node_modules/es3ify/node_modules/esprima-fb/esprima.js:4682:20) at parseStatementList (/Users/nolan/workspace/pouchdb-replication-stream/node_modules/es3ify/node_modules/esprima-fb/esprima.js:3274:25) at parseBlock (/Users/nolan/workspace/pouchdb-replication-stream/node_modules/es3ify/node_modules/esprima-fb/esprima.js:3289:17) at /Users/nolan/workspace/pouchdb-replication-stream/node_modules/es3ify/node_modules/esprima-fb/esprima.js:5832:38 at parseStatement (/Users/nolan/workspace/pouchdb-replication-stream/node_modules/es3ify/node_modules/esprima-fb/esprima.js:4088:24)
— Reply to this email directly or view it on GitHub https://github.com/nolanlawson/pouchdb-replication-stream/issues/8.
still seeing this on npm run build
Yeah why don't we remove es3ify for now? On Oct 21, 2014 5:33 AM, "Jan Lehnardt" notifications@github.com wrote:
still seeing this on npm run build
— Reply to this email directly or view it on GitHub https://github.com/nolanlawson/pouchdb-replication-stream/issues/8#issuecomment-59902025 .
Good idea: https://github.com/nolanlawson/pouchdb-replication-stream/pull/11 :)
things work now
This has been fixed last I checked.
wtf?