laravel-mix: Cannot find module webpack.mix

Mix needs to have a webpack.mix.js file in the project root, so if it can’t find one, it makes sense that it will fail. I don’t think there’s anything we can do to this repo to fix your issue.

A lot of people prefer to do their production builds locally.

Webpack-mix is a huge shitstorm and I’d recommend not to use it, indeed fuck you Jeffrey ^^

Hi @aspitzer! My workaround for using a symlinked node_modules folder was to copy/paste the webpack.config.js from this repo to my project root (sibling to webpack.mix.js and package.json).

Then, I added a line to the copied file before Mix.initialize() which corrects the root path to the current directory (not the location of the symlinked modules):

// imports...

/**
 * Set the root path to where this current file is. Since we symlink
 * node_modules on production, Mix thinks we are in the shared folder instead
 * of the current build folder, which causes a failed build.
 */
Mix.Paths.setRootPath( path.resolve(__dirname) );

Mix.initialize();

Finally, I updated the production script inside package.json to "node node_modules/cross-env/bin/cross-env.js NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --config=webpack.config.js"

This is necessary because the constructor value for Mix.Paths.root() uses path.resolve() to find the current context. I don’t know NodeJS well enough to suggest an alternative approach, and the workaround above works fine for me 😃

cc https://github.com/JeffreyWay/laravel-mix/issues/386

I know this is old but running npm install laravel-mix fixed my issue.

This fix does not work on newest version? Anyone has fix?

@JeffreyWay - this may not be the best place to ask this, but your comment that a lot of people prefer to do their builds locally … I would love to do my builds locally, but there are a few reasons why I feel it doesn’t work:

1. It means that I have to remember to re-compile everything before I deploy. Sure, it could be part of my deployment process (tagging the release, merging into the main branch, etc) but it feels like a completely unnecessary step and could easily accidentally release with a non-optimized/source-mapped site.
2. When multiple people are working on a project, it results in a great deal of merge conflicts if everyone’s compiled assets are checked in.

I’d love to know what the best practices for this are, because these sure don’t seem like good practices at all.

@JeffreyWay I’m pretty sure is a problem with envoyer and symbolic links. Folder where project is deployed is on the current. And node_modules is a symbolic link. I think problem is when on the node_modules tryes to go up a directory and that directory is not laravel root. (because node_modules is a symbolic link to avoid download everything on every deploy)

So is looking in this directory: /home/forge/XXX/storage/app/webpack.mix

When it should be looking here: /home/forge/XXX/current/webpack.mix

surprised it wasn’t solved. Was running into the same issue.

A lot of people prefer to do their production builds locally.

And a lot of people don’t, simply because production server has more ram/cores/better hdd and other reasons. Both ways is ok.

Hi @JeffreyWay. Why not check for an environment variable to define the root path? If the variable is not defined, fallback to the automatic root path detection.

I don’t see why webpack is perfectly fine being able to resolve to a webpack configuration file from a symlinked node_modules directory but this can not be properly solved for laravel-mix. I have been struggling for this for an hour now because of the confusing import fest within laravel-mix.

Laravel-mix is simplying trying to resolve something relatively while Webpack is doing something entirely different to fetch the default webpack config.

I hope I can respond with some more information if I figure this out.

@cerw Thanks for your idea. But all in all, I decided to realize the idea of @jplhomer
copy webpack.config.js in a root directory and modify composer.json for it. Start of the webpack.config.js file:

require(__dirname + '/node_modules/laravel-mix/src/index');
Mix.paths.setRootPath( path.resolve(__dirname) );
require(Mix.paths.mix());

Anyway, I hope that Jeffrey will fix it in the next releazes.

And there is definitely a storage/app/webpack.mix.js file?