question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Webpack fails to build on NTFS filesystems

See original GitHub issue

Do you want to request a feature or report a bug? I am reporting a bug.

What is the current behavior? The latest version of webpack 3.5.5 (as well as the beta version) does not build on NTFS filesystems. Specifically, the error occurs at the postinstall step, and seems to be caused by an attempt to remove a directory with contents using rmdir.

If the current behavior is a bug, please provide the steps to reproduce. This gist reproduces the bug on my machine. Note that this assumes a Linux OS.

What is the expected behavior? The build should not fail.

Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.

$ npm --version
5.4.0
$ uname -v
#37~16.04.1-Ubuntu SMP Fri Aug 11 14:07:24 UTC 2017
$ cat /proc/version
Linux version 4.10.0-33-generic (buildd@lgw01-22) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #37~16.04.1-Ubuntu SMP Fri Aug 11 14:07:24 UTC 2017

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:7 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
NemoSteincommented, Sep 11, 2017

Since I’m on a Windows 10 I can’t confirm the relation with NTFS, but the problem might be with npm itself… I was able to install webpack with npm@5.3.0, but failed with npm@5.4.1 with a EPERM, so the problem must be in npm@5.4.0, since that is the version you used. Marking the installation with --no-optional worked.

I think that this issue should be opened again…

0reactions
sheljohncommented, Sep 4, 2017

@sokra I think that’s a problem solved 😃

Installing with yarn add webpack

This installs with a warning regarding fsevents being incompatible with the platform.

Installing with npm i webpack --no-optional

This works fine on my machine, no error or warning during the build.

Installing fsevents on Linux

This was off to a bad start, because the package specifies explicitly that it is for OSX only. The installation fails with npm, and throws a warning with yarn for the same reason: “incompatible platform”.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Error: EACCES: permission denied, lstat '/mnt/c/...' · Issue #187 ...
I run webpack --watch --watch-options-stdin ... and amidst its initial build (not the subsequent builds triggered by changed files), ...
Read more >
Typescript Webpack React compilation resulting in read only ...
I am currently trying to compile my project with React, Webpack, and Typescript. ... Failed at the typescript_react@1.0.0 build script.
Read more >
Npm package installation error on other partition
I'm using Linux 5.15.32-1-MANJARO . I've read that it has ntfs support maybe I'll try removing the ntfs-3g first.
Read more >
Fix corrupt NTFS partition without Windows - Ask Ubuntu
I'm putting the debug output of fdisk and blkid here. At the same time, any OS is unable to mount my root partition,...
Read more >
Webpack fails to load TS files? - Medium
I wanted to use the angular Webpack loader to compile normal Typescript. However, when I ran Webpack in watch mode, things stopped working....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found