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 5 can't set output path to `/`

See original GitHub issue

Bug report

What is the current behavior?

When the output.path is set to /, webpack 5 will fail with an EISDIR error. It works in webpack 4. / is commonly used when targeting an in-memory filesystem such as https://github.com/streamich/memfs; we used it quite often in tests.

If the current behavior is a bug, please provide the steps to reproduce.

git clone https://github.com/sodatea/webpack-rootdir-bug.git
cd webpack-rootdir-bug
yarn && yarn build

What is the expected behavior?

Should successfully build.

Other relevant information: webpack version: v5.0.0-beta.14 Node.js version: v12.16.1 Operating System: macOS Catalina 10.15.3 Additional tools: None

Issue Analytics

State:
Created 4 years ago
Comments:7 (7 by maintainers)

Top GitHub Comments

1reaction

sodateacommented, Mar 12, 2020

See the linked pull request.

memory-fs throws EEXIST, which webpack’s fs.mkdirp implementation could recognize. But BSD systems and memfs throws EISDIR. The refactored fs.mkdirp in webpack 5 couldn’t handle that error and fails.

0reactions

alexander-akaitcommented, Jan 31, 2021

Still valid