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.
🙌 Migrating to WPGulp v2.0.0
See original GitHub issueThis issue is here to maintain a list of issues that you might face while migrating to or testing the new version of WPGulp i.e. version 2.0.0. Take a look at #61.
- Run
npm i -g gulp-cliif you run into some weird issues like these.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Migrating from WordPress to Gatsby - Edvins Antonovs
My story behind ditching PHP and migrating WordPress website to ... Initial version (v.1.0.0) of edvins.io was built around 2 years ago ...
Read more >wp-gulp - npm
Start using wp-gulp in your project by running `npm i wp-gulp`. There are no other projects in the npm registry using wp-gulp.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@asharirfan That’s why I wrote it there. It’s needed since you might have installed an older version of Gulp CLI globally. Also update your Node and NPM. Your versions are way too old.
It becomes
npm run. I recently made this change on JointsWP and it cut back on the amount of Node/NPM related support tickets quite a bit.There are other benefits to using
npm runas well. It’d make it an easy transition to NPM scripts if you ever wanted to implement them.