Pixi.js: npm will not install any version of v5 except for 5.1.1

[bgenchel]

Expected Behavior

when, in my package.json, I specify a different version of pixi.js, such as 5.0.4, as in
"pixi.js": "5.0.4",
npm install should install that version of pixi.js, and not v5.1.1

Current Behavior

every time i've tried this, even after deleting node_modules/ and package-lock.json, 5.1.1 is always installed.

Additionally, when the installation is running, in my terminal, I can see it says [email protected] postinstall ..., but when I open my browser and run my app, I get PixiJS 5.1.1 in the console.

Possible Solution

I have no idea what the solution could be. I don't really know why this is happening.

Steps to Reproduce

in package.json, change your pixi.js version to a version above 5, but not 5.1.1, then run npm install. Additionally, try first deleting your node_modules/ folder and package-lock.json file.

Environment

• pixi.js version: trying to be any version of 5 besides 5.1.1
• Browser & Version: _e.g. Chrome 75.0.3770.142
• OS & Version: Mac OSX High Sierra

[Dawnlee]

I have the same problem. Have you solved it? I have try set npm config save-exact true,but it doesn't work.

[bgenchel]

I have not unfortunately :(

[dylanbox]

@bgenchel Can you drop what you have in your package_lock.json? I have a feeling like the individual Pixi packages aren't installing the version you're expecting. If you notice under the pixi.js item, it will have an a requires object with each of the individual packages and what the expected version is. The version expected might be prepended with a ^ which will match the individual packages to the most recent minor version. (For example "^5.0.4" will match the most recent "5.x.x" version, "5.1.1" in your case)

You can solve this by locking the individual modules to a specific version, but I believe you would have to include them each in your package.json

[bigtimebuddy]

Hmm, I'm starting to consider using the Lerna publishing command --exact which will lock the version instead of the semver range when publishing. That would fix this issue.