For advanced users and advanced uses, there are some additional build processes. You can find them under
package.json all the way at the bottom under scripts.
Here we have all the different processes you can run using the “npm run” command. If you’ve followed the course, you should be familiar with two of these commands already: “npm run dev” and “npm run build”
“npm run dev” – This is the process that builds the entire theme, then spins up a browser sync and watches all of your files.
“npm run bundle” – This bundles out the theme, and creates a separate folder and separate zip archive for when you’re done building.
“npm run build” – This runs the entire build process without running browser sync and watch. So if you just want to spin up the theme once to see what it produces, you just say “npm-run build”, and you have “npm run gulp” if you want to target specific Gulp processes.
You have the option to run any of the Gulp processes that sit inside the Gulp folder. Most of these processes are being run automatically in the other scripts, but if you want to target a Gulp process specifically, you can do this by running “npm run gulp [script]”. For example, to run the images Gulp processes, you will run “npm run gulp images”. Or to run the PHP process to check your code against current PHP coding standards, you’d run “npm run gulp php”.
These are advanced features which are for advanced purposes, but they are available to you. They’re also a good path into understanding how WP Rig works better.
So if you’re ever curious about what’s going on, go check out “package.json” or the folder “/gulp” and see how the Gulp processes are built together to make everything work properly.