This repository has been archived by the owner. It is now read-only.

can't run npm after upgrading to 5.5.1 #18856

Closed
vesper8 opened this Issue Oct 16, 2017 · 3 comments

Comments

Projects
None yet
3 participants
@vesper8

vesper8 commented Oct 16, 2017

everything was fine on 5.4.2, then I ran an upgrade. Even deleted node_modules and did a fresh npm install

getting these errors on 5.5.1

fs.js:682
  return binding.read(fd, buffer, offset, length, position);
                 ^

Error: EISDIR: illegal operation on a directory, read
    at Object.fs.readSync (fs.js:682:18)
    at tryReadSync (fs.js:543:20)
    at Object.fs.readFileSync (fs.js:586:19)
    at Function.concatenate.sync (/Volumes/DEV/www.mydomain.com/node_modules/concatenate/lib/concatenate.js:122:17)
    at FileCollection.merge (/Volumes/DEV/www.mydomain.com/node_modules/laravel-mix/src/FileCollection.js:31:36)
    at ConcatenateFilesTask.merge (/Volumes/DEV/www.mydomain.com/node_modules/laravel-mix/src/tasks/ConcatenateFilesTask.js:20:24)
    at ConcatenateFilesTask.run (/Volumes/DEV/www.mydomain.com/node_modules/laravel-mix/src/tasks/ConcatenateFilesTask.js:11:14)
    at CustomTasksPlugin.runTask (/Volumes/DEV/www.mydomain.com/node_modules/laravel-mix/src/plugins/CustomTasksPlugin.js:34:14)
    at Mix.tasks.forEach.task (/Volumes/DEV/www.mydomain.com/node_modules/laravel-mix/src/plugins/CustomTasksPlugin.js:9:44)
    at Array.forEach (<anonymous>)
    at Compiler.compiler.plugin.stats (/Volumes/DEV/www.mydomain.com/node_modules/laravel-mix/src/plugins/CustomTasksPlugin.js:9:23)
    at Compiler.applyPlugins (/Volumes/DEV/www.mydomain.com/node_modules/tapable/lib/Tapable.js:61:14)
    at Watching._done (/Volumes/DEV/www.mydomain.com/node_modules/webpack/lib/Compiler.js:104:17)
    at compiler.emitRecords.err (/Volumes/DEV/www.mydomain.com/node_modules/webpack/lib/Compiler.js:78:19)
    at Compiler.emitRecords (/Volumes/DEV/www.mydomain.com/node_modules/webpack/lib/Compiler.js:375:38)
    at compiler.emitAssets.err (/Volumes/DEV/www.mydomain.com/node_modules/webpack/lib/Compiler.js:61:20)
    at applyPluginsAsyncSeries1.err (/Volumes/DEV/www.mydomain.com/node_modules/webpack/lib/Compiler.js:368:12)
    at next (/Volumes/DEV/www.mydomain.com/node_modules/tapable/lib/Tapable.js:218:11)
    at Compiler.compiler.plugin (/Volumes/DEV/www.mydomain.com/node_modules/webpack/lib/performance/SizeLimitsPlugin.js:99:4)
    at Compiler.applyPluginsAsyncSeries1 (/Volumes/DEV/www.mydomain.com/node_modules/tapable/lib/Tapable.js:222:13)
    at Compiler.afterEmit (/Volumes/DEV/www.mydomain.com/node_modules/webpack/lib/Compiler.js:365:9)
    at require.forEach.err (/Volumes/DEV/www.mydomain.com/node_modules/webpack/lib/Compiler.js:354:15)
    at /Volumes/DEV/www.mydomain.com/node_modules/webpack/node_modules/async/dist/async.js:421:16
    at iteratorCallback (/Volumes/DEV/www.mydomain.com/node_modules/webpack/node_modules/async/dist/async.js:998:13)
    at /Volumes/DEV/www.mydomain.com/node_modules/webpack/node_modules/async/dist/async.js:906:16
    at /Volumes/DEV/www.mydomain.com/node_modules/graceful-fs/graceful-fs.js:43:10
    at FSReqWrap.oncomplete (fs.js:136:15)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ watch: `cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --watch --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @ watch script.

work fine again after downgrading back to npm@5.4

@KenanY KenanY added the support label Oct 16, 2017

@KenanY

This comment has been minimized.

Show comment
Hide comment
@KenanY

KenanY Oct 16, 2017

Member

@vesper8 node --version?

Member

KenanY commented Oct 16, 2017

@vesper8 node --version?

@vesper8

This comment has been minimized.

Show comment
Hide comment
@vesper8

vesper8 commented Oct 16, 2017

@KenanY 8.7.0

@npm-robot

This comment has been minimized.

Show comment
Hide comment
@npm-robot

npm-robot Oct 27, 2017

We're closing this support issue as it has gone three days without activity. The npm CLI team itself does not provide support via this issue tracker, but we are happy when users help each other here. In our experience once a support issue goes dormant it's unlikely to get further activity. If you're still having problems, you may be better served by joining WeAllJS and asking your question in its #npm channel. The npm CLI team is all present there, but there are also lots of other folks who can help you too.

For more information about our new issue aging policies and why we've instituted them please see our blog post.

npm-robot commented Oct 27, 2017

We're closing this support issue as it has gone three days without activity. The npm CLI team itself does not provide support via this issue tracker, but we are happy when users help each other here. In our experience once a support issue goes dormant it's unlikely to get further activity. If you're still having problems, you may be better served by joining WeAllJS and asking your question in its #npm channel. The npm CLI team is all present there, but there are also lots of other folks who can help you too.

For more information about our new issue aging policies and why we've instituted them please see our blog post.

@npm-robot npm-robot closed this Oct 27, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.