In the same directory where you have package.json create an npm-shrinkwrap. 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 that's known to work under Node v12 - that's the option I've chosen, let me tell how to use it. 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Ĭ. Brief content visible, double tap to read full content. Ob und wann dieser Artikel wieder vorrätig sein wird, ist. 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.ī. Nike Fs Lite Run 3 Laufschuh 3,0 von 5 Sternen 1 Sternebewertung. 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)
