Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

'npm start' fails with 'SyntaxError: Assigning to rvalue'

See original GitHub issue

Hallo 👋, I’m seeing the error SyntaxError: Assigning to rvalue when creating a new app with create-choo-app.

Environment;

macOS Sierra 10.12.16
node 8.9.4
npm 5.6.0
npx 9.7.1

Commands;

npx create-choo-app choo-example
cd choo-example
npm start

Error;

(node:96280) ExperimentalWarning: The http2 module is an experimental API.
scripts:browserify.bundle Assigning to rvalue (3:45)
SyntaxError: Assigning to rvalue (3:45)
    at Parser.pp$4.raise (/projects/choo-example/node_modules/acorn/dist/acorn.js:2684:13)
    at Parser.pp$2.toAssignable (/projects/choo-example/node_modules/acorn/dist/acorn.js:1581:12)
    at Parser.pp$3.parseMaybeAssign (/projects/choo-example/node_modules/acorn/dist/acorn.js:1885:47)
    at Parser.pp$3.parseExpression (/projects/choo-example/node_modules/acorn/dist/acorn.js:1851:19)
    at Parser.pp$1.parseStatement (/projects/choo-example/node_modules/acorn/dist/acorn.js:809:45)
    at Parser.pp$1.parseTopLevel (/projects/choo-example/node_modules/acorn/dist/acorn.js:700:23)
    at Parser.parse (/projects/choo-example/node_modules/acorn/dist/acorn.js:545:15)
    at parse (/projects/choo-example/node_modules/acorn/dist/acorn.js:3741:37)
    at module.exports (/projects/choo-example/node_modules/falafel/index.js:22:15)
    at /projects/choo-example/node_modules/static-module/index.js:30:13

Issue Analytics

State:
Created 6 years ago
Comments:7 (7 by maintainers)

Top GitHub Comments

2reactions

chrisdwheatleycommented, Feb 9, 2018

Thanks for the help @goto-bus-stop, that does look to be the issue.

Because I’ve previously installed versions of a lot of the dependencies it looks like a few of them were out of date, rather than updating each I ran npm cache clean --force.

It looks like this has caused issues previously and @yoshuawuyts suggested removing the --cache-min flag, I’m going to submit a PR to do that.

0reactions

chrisdwheatleycommented, Feb 13, 2018

Thanks @yoshuawuyts 👍!