NPM Dev and NPM Watch GONE After move to Laravel Valet

Published 6 months ago by jgravois

Last weekend I finally ditched MAMP PRO and installed Laravel Valet. I couldn't be happier and have worked fine all week until this morning. I tried to run npm run watch and got this message

npm ERR! Darwin 16.5.0
npm ERR! argv "/usr/local/bin/node" "/Users/jgravois/.npm-packages/bin/npm" "run" "watch"
npm ERR! node v6.10.3
npm ERR! npm  v4.0.2

npm ERR! missing script: watch

I loaded the latest versions of npm and node and updated to the latest version of Laravel Mix.

I then tried to run npm run dev so I could at least see my changes and now I get this

> @ dev /Users/jgravois/Documents/Code/teamsite
> gulp watch

[08:12:32] Using gulpfile ~/Documents/Code/teamsite/gulpfile.js
[08:12:32] Starting 'watch'...
[08:12:32] Starting 'browserify'...

Fetching Browserify Source Files...
   - resources/assets/js/main.js


Saving To...
   - public/js/main.js

[08:12:33] Finished 'browserify' after 597 ms
[08:12:33] Finished 'watch' after 956 ms
[08:12:38] 984952 bytes written (4.24 seconds)
[08:12:38] gulp-notify: [Laravel Elixir] Browserify Compiled!

OMG ... LOL .... I don't HAVE a gulpfile ... I have a webpack.mix.js file. AND I don't have Elixir installed ... I have Mix.

My site in the browser won't load with the following in the console

app.js:101750 Uncaught Error: Module build failed: Error: Couldn't find preset "es2015" relative to directory "/Users/jgravois/code/teamsite/node_modules/vue2-google-maps"
    at /Users/jgravois/code/teamsite/node_modules/babel-core/lib/transformation/file/options/option-manager.js:293:19
Best Answer (As Selected By jgravois)
jgravois

Relieved and Red-Faced

My terminal alias was pointing to the OLD version in the "other" code directory (~/Documents/Code) instead of the "new" code directory (~/code).

npm run works when I am in the RIGHT directory!

jgravois

Relieved and Red-Faced

My terminal alias was pointing to the OLD version in the "other" code directory (~/Documents/Code) instead of the "new" code directory (~/code).

npm run works when I am in the RIGHT directory!

Please sign in or create an account to participate in this conversation.