Remove watch script and update start script

[aurooba]

Closes #150
Closes #81

I'm not entirely sure why wp-scripts doesn't always detect new files, but I decided to side step it with the existing nodemon setup. Now instead of running npm run watch, you can just run npm run start for a faster development build, which will work anytime a js, css, scss, jsonc, php, or json file is added or changed.

[bacoords]

I get this error FYI and running dev:compile opens up the watch (maybe for the theme.json) and leaves it open:

[1] [webpack-cli] Error: Unknown option '--no-watch'
[1] [webpack-cli] Run 'webpack --help' to see available commands and options

[aurooba]

@bacoords I fixed the part where dev:compile stays open, but I am unable to recreate the error you shared. What script did you get that error on?

[bacoords]

npm run dev:compile which has it as a flag:

"dev:compile": "concurrently \"npm run themejson\" \"wp-scripts start --config ./bin/webpack.config.js --webpack-src-dir=src/blocks --no-watch\"",

But I can confirm the other fix worked

[aurooba]

Hmm. That's odd. What version of node and npm are you running?

[bacoords]

bacoords@MacBook-Pro-5 tangent % node -v
v16.14.0
bacoords@MacBook-Pro-5 tangent % npm -v
8.3.1

[bacoords]

The "--no-watch" issue is fixed but was an issue due to webpack (installed as a dependency for wp-scripts) was outdated.