Laravel Mix suddenly started to give errors

I think I also need to mention that I had updated node and npm on my mac.

[email protected]
[email protected]

Might be worth trying the LTS version of node to see if that makes a difference

I've tried Node 6.9.5, no luck here, so I'm back at 7.5.0.

When I downgrade laravel-mix to 0.6.0 the script runs as expected! versions 0.6.1 and up fail.

More information needed:

terminal output

laravel-mix version

@forehalo it fails on laravel-mix version 0.6.1, 0.6.2 and 0.6.3.

Here is the output with laravel-mix 0.6.3

 ERROR  Failed to compile with 10 errors

These dependencies were not found in node_modules:

* ../fonts/bootstrap/glyphicons-halflings-regular.eot
* ../fonts/bootstrap/glyphicons-halflings-regular.woff2
* ../fonts/bootstrap/glyphicons-halflings-regular.woff
* ../fonts/bootstrap/glyphicons-halflings-regular.ttf
* ../fonts/bootstrap/glyphicons-halflings-regular.svg
* ../fonts/bootstrap/glyphicons-halflings-regular.eot
* ../fonts/bootstrap/glyphicons-halflings-regular.woff2
* ../fonts/bootstrap/glyphicons-halflings-regular.woff
* ../fonts/bootstrap/glyphicons-halflings-regular.ttf
* ../fonts/bootstrap/glyphicons-halflings-regular.svg

Did you forget to run npm install --save for them?                                                                                                                                                                                                                                                                                                Asset       Size  Chunks                    Chunk Names
/admin_assets/js/vendor.f57e0dbf4c39091c77d2.js    1.85 MB    0, 3  [emitted]  [big]  /admin_assets/js/vendor
  /admin_assets/js/main.d9fe4985014bba757801.js     914 kB    1, 3  [emitted]  [big]  /admin_assets/js/main
        /assets/js/main.0521e1ba0354928d5e7e.js    73.4 kB    2, 3  [emitted]         /assets/js/main
    /assets/js/manifest.d41d8cd98f00b204e980.js    5.65 kB       3  [emitted]         /assets/js/manifest
                              mix-manifest.json  306 bytes          [emitted]         

npm ERR! Darwin 16.4.0
npm ERR! argv "/usr/local/Cellar/node/7.5.0/bin/node" "/usr/local/bin/npm" "run" "dev"
npm ERR! node v7.5.0
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! @ dev: `node node_modules/cross-env/bin/cross-env.js NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js`
npm ERR! Exit status 2
npm ERR! 
npm ERR! Failed at the @ dev script 'node node_modules/cross-env/bin/cross-env.js NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the  package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node node_modules/cross-env/bin/cross-env.js NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs 
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls 
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/myuser/projects/myproject/npm-debug.log

@stefr How to update/downgrade laravel-mix?

@Slon Go to your package.json file.

change "laravel-mix": "^0.6.0" into (for example) "laravel-mix": "0.6.1" Then run npm install

see #328

@forehalo laravel-mix just got updated to 0.7.0 I can confirm that this solves the problem!

Hello all,

I'm still very new to Laravel, but I just had this same problem crop up, but then realized that I had made a very simple mistake and wanted to share in case others were having this problem and had done the same thing.

I use PHPStorm as my IDE and when I went to my app.scss file I realized I had added a leading '/' to my import for bootstrap because it was underlined red due to the IDE telling me it couldn't resolve the directory.

But adding that leading '/' as below just before 'node_modules':

@import "/node_modules/bootstrap-sass/assets/stylesheets/bootstrap";

• is what caused it to error out on me. I got lucky and removed it to prove a theory that webpack will do the resolving and it worked. I came to this post because the OP talked about removing all SCSS files and it was working again (which happened for me as well).

Again this was a simple mistake and what is causing the same error for others could be something else entirely and I could be misunderstanding this, but just to save anyone else the headache incase they ended up doing the same thing as I did.