Laravel-mix: webpack.js: Permission denied

[gavinbenda]

Not quite sure what is happening, as this was working at some stage on this machine with a previous version.

[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

• Node Version: 7.9.0
• NPM Version: 4.5.0
• OS: Ubuntu (Vagrant/Homestead VM)

Description:

Getting the following on a brand new install of Laravel 5.4, no files changed or altered.
Trying: npm run dev, also sudo npm run dev
Also tried chmodd'ing the webpack file it's complaining about.
Installed via npm install --no-bin-links
Have tried completely purging the node_modules and clearing the npm cache.

> @ dev /home/vagrant/webdev/laravel-test/testapp
> npm run development


> @ development /home/vagrant/webdev/laravel-test/testapp
> cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js

/bin/sh: 1: node_modules/webpack/bin/webpack.js: Permission denied
npm ERR! code ELIFECYCLE
npm ERR! errno 126
npm ERR! @ development: `cross-env 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 126
npm ERR!
npm ERR! Failed at the @ development script 'cross-env 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!     cross-env 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.

Debug Log:

0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node',
1 verbose cli   '/usr/local/bin/npm',
1 verbose cli   'run',
1 verbose cli   'development' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'predevelopment', 'development', 'postdevelopment' ]
5 info lifecycle @~predevelopment: @
6 silly lifecycle @~predevelopment: no script for predevelopment, continuing
7 info lifecycle @~development: @
8 verbose lifecycle @~development: unsafe-perm in lifecycle true
9 verbose lifecycle @~development: PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/home/vagrant/webdev/laravel-test/testapp/node_modules/.bin:/usr/local/lib/node_modules/npm/bin/node-gyp-bin:/home/vagrant/webdev/laravel-test/testapp/node_modules/.bin:/home/vagrant/.composer/vendor/bin:/usr/local/sbin:/usr/local/bin$
10 verbose lifecycle @~development: CWD: /home/vagrant/webdev/laravel-test/testapp
11 silly lifecycle @~development: Args: [ '-c',
11 silly lifecycle   'cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js' ]
12 silly lifecycle @~development: Returned: code: 126  signal: null
13 info lifecycle @~development: Failed to exec development script
14 verbose stack Error: @ development: `cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js`
14 verbose stack Exit status 126
14 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:279:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:194:7)
14 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:194:7)
14 verbose stack     at maybeClose (internal/child_process.js:899:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid @
16 verbose cwd /home/vagrant/webdev/laravel-test/testapp
17 verbose Linux 4.4.0-22-generic
18 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "development"
19 verbose node v7.9.0
20 verbose npm  v4.5.0
21 error code ELIFECYCLE
22 error errno 126
23 error @ development: `cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js`
23 error Exit status 126
24 error Failed at the @ development script 'cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js'.
24 error Make sure you have the latest version of node.js and npm installed.
24 error If you do, this is most likely a problem with the  package,
24 error not with npm itself.
24 error Tell the author that this fails on your system:
24 error     cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js
24 error You can get information on how to open an issue for this project with:
24 error     npm bugs
24 error Or if that isn't available, you can get their info via:
24 error     npm owner ls
24 error There is likely additional logging output above.
25 verbose exit [ 126, true ]

[QWp6t]

Does it work if you run node on the host OS instead of within the VM?

[JeffreyWay]

@gavinbenda Do you have cross-env installed locally? npm install cross-env -D

[choyan]

npm rebuild fixes my problem.

[devenpateldp]

if you are using mount drive check this option.

in /etc/fstab file add exec in the mount option, like this:

auto,user,exec,utf8,uid=1000,gid=1000,rw 0 0

[mcansky]

@devenpateldp thanks for your comment : it made me realise there was probably an issue with my separate mount and it fixed the issue

[devenpateldp]

Great!

[lautarochiavarino]

@devenpateldp you save my life! i love you a little.

[devenpateldp]

Great!!!!!!

On Tue, Sep 29, 2020 at 3:59 AM lautarochiavarino [e-mail]
wrote:

@devenpateldp https://github.com/devenpateldp you save my life! i love
you a little.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/JeffreyWay/laravel-mix/issues/726#issuecomment-700317425,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHR4QTMJBFJHVZSKYKFVCLSIEE5PANCNFSM4DIPGRRA
.

--
https://about.me/deven.patel?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=gmail_api
Mr. Deven Patel
skype: devenpateldp