Parsing Errors in Acorn with v9 (not in v8)
See original GitHub issuescripts:browserify.bundle Unexpected token (8:60) SyntaxError: Unexpected token (8:60)
at Parser.pp$4.raise (/Users/paul/GitHub/books/node_modules/acorn/dist/acorn.js:2610:13)
at Parser.pp.unexpected (/Users/paul/GitHub/books/node_modules/acorn/dist/acorn.js:637:8)
at Parser.pp.semicolon (/Users/paul/GitHub/books/node_modules/acorn/dist/acorn.js:614:64)
at Parser.pp$1.parseExpressionStatement (/Users/paul/GitHub/books/node_modules/acorn/dist/acorn.js
I kept getting this error. When I didn’t get this error, I got the message in the browser that I had no routes (there’s only one /*
route). Going back to v8 fixed this issue.
My repo is here: https://github.com/AutoSponge/books. Based on what was happening before on MacOSX, node v8.7.0, if you change bankai to latest, it will start getting flaky.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
ES3 reserved words · Issue #15017 · eslint/eslint - GitHub
As an option, instead of parsing error, it can be a new rule that will forbid the usage of ES3 reserved words as...
Read more >Acorn - why arrow function throws parsing error?
Question: why Acorn throws an exception while parses arrow function? When I change parse to: componentDidMount(){ // do some stuff here... }.
Read more >Npm package installation error on other partition
I'm getting this error whenever I install a package from npm on another partition: npm ERR! code 126 npm ERR! path ...
Read more >espree | Yarn - Package Manager
In Espree, the end of a node is where the last token occurs. Espree does not parse let and const declarations by default....
Read more >Implementing a runtime version of JSX – The Guild
Essentially there are 3 things we should figure out when parsing a JSX code: The name / component of the React element. The...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
yep, common-shakeify was generating incorrect output when using an arrow function in
exports.xyz = () => {}
, so the next plugin would not be able to parse it. fixed in 0.4.3.Yay, happy it worked out alright! ☺️
On Fri, Oct 20, 2017 at 7:46 PM Paul Grenier notifications@github.com wrote: