`npx` causing issues with Yarn

• Laravel Mix Version: ^6.0.18 (npm list --depth=0)
• Node Version (node -v): v14.16.0
• NPM Version (npm -v): 6.14.11
• Yarn Version: 2.x and 3.0.0-rc.2
• OS: macOS 11.2.3

Description:

The watch and build commands run npx under the hood. This causes issues when using Yarn as the package manager and forces users to install webpack and webpack-cli as dependencies manually resulting in a confusing experience.

Steps To Reproduce:

• Create a project using Yarn as the package manager
• Add laravel-mix as a dev dependency
• Add a webpack.mix file (or compatible variant)
  • This only needs to contain the import at the top of the file (const mix = require('laravel-mix');)
• Run mix using Yarn — yarn mix

On first run, the user is prompted to install webpack-cli. If the user chooses to install at that time, the command then subsequently fails as it can’t find webpack. In order to fix this issue, webpack must also be installed as a dev dependency.

Solution:

Rather than running these commands with npx, build and watch should call webpack directly and both webpack and webpack-cli should be listed as peer dependencies.

[zulaica]

Something we could do is run npx if running under npm and yarn run webpack if running via yarn — I think that’d work? I’d have to do some testing to check.

I can give that a shot. I’ve got everything all set up and running at the moment, so it’s worth trying and reporting back.

[thecrypticace]

Something we could do is run npx if running under npm and yarn run webpack if running via yarn — I think that’d work? I’d have to do some testing to check.