npm3 script, use deprecated version of estraverse

[adriengibrat]

I'm having ExportDefaultDeclaration error with npm3 using standard v5.3.1 in npm script ... but no error when using it in cli!

This bug is resolved.

But with npm3, when using standard via a npm script, a deprecated version of estraverse (see RReverser/estraverse-fb#5) is used.

It's related on how npm3 resolves dependencies. I did not checked the dependency tree to check if there is peer dependencies...

It's not a bug in standard, but I created an issue here to avoid anyone to spend too much time to track this down.

[feross]

It sounds like you have two copies of standard installed. One global (used by the CLI) and one local (used by npm run scripts). You can update both to the latest version by running:

npm install standard -g
npm install standard@latest --save-dev

[dcousens]

@feross is @latest not required for -g?

[feross]

npm install -g always uses the latest version from npm. The reason you need @latest for local install is that there could be an old version specified in package.json and npm install will obey the semver restrictions.

[dcousens]

TIL, thanks :)

[feross]

https://docs.npmjs.com/cli/install is really interesting, fwiw 👍

[adriengibrat]

Yep, I have both global and local standard installed. But both are v5.3.1, so it's not just a version pb.

The pb is when local standard is called via npm script, it use the deprecated version of estraverse because of estraverse-fb deprecated dependency.

The bug seems to be related to npm3 dependencies collision handling: npm/npm#9708

I worked around the pb, doing this: npm/npm#9708 (comment)

[feross]

Closing this now, since it's not a standard issue.