Anything specified in this file cant be overridden by package.json content, which gives us what we need: pinning graceful-fs at 4.2. Anything specified in this file can't be overridden by package.json content, which gives us what we need: pinning graceful-fs at 4.2.2 despite whatever gulp 3 requires in package.json. To pin graceful-fs to version 4.2.2, we need to use an npm-shrinkwrap.json file, which lets you lock down the versions of installed packages and their descendant packages. To pin graceful-fs to version 4.2.2, we need to use an npm-shrinkwrap.json file, which lets you lock down the versions of installed packages and their descendant packages.
GIFSICLE PACKAGE.JSON HOW TO
To pin graceful-fs to version 4.2.2 that's known to work under Node v12 - that's the option I've chosen, let me tell how to use it. After that, I have launch npm install and now its OK. In the devDependencies, I have upgrade the version of jpegtran-bin 0.2.0 to 0.2.6. To downgrade Node to v11 - is also not an option to me, I don't want to jump through nvm hoops or even think about juggling node environmentsĬ. I have the same problem and I have resolve it with edit my package.json file. I've searched through my entire project, there are no other references to gifsicle. Only the gifsicle0.1.7 version was back, even though I have gifsicle3.0.3 in my package.json file. So I cleared them, and reran 'npm install'. To upgrade gulp to v4 - to me, that's not an option, and I don't want to re-write and re-config my frontend toolchain for Xth time.ī. So I checked the cache, and both the 3.0.3 and the 0.1.7 files were in there. The thing is, gulp v3 doesn't work (as of now) under node v12, because it depends on which patches Node's fs module and that patch worked before node v12 just fine. Are you getting a ReferenceError: primordials is not defined error message when trying to run gulp? Chances are you're on gulp v3 and node v12, and that's the source of the issue.
0 kommentar(er)
