Replies: 11 comments 14 replies
-
Sounds like you don't update all deps, please run |
Beta Was this translation helpful? Give feedback.
-
I ran the command and this is the result
What should I do next? |
Beta Was this translation helpful? Give feedback.
-
Working root main config
Broken
|
Beta Was this translation helpful? Give feedback.
-
What's the advantage of using those settings? I read from the webpack docs that lazyload is still experimental. Do you want me to do a test with the fscache disabled and lazyload enabled? |
Beta Was this translation helpful? Give feedback.
-
I was able to pinpoint that the problem is caused by lazyCompilation (I don't know why I said lazyLoading before). Now the error is gone.
|
Beta Was this translation helpful? Give feedback.
-
fsCache: true and removing the addon works fine.
|
Beta Was this translation helpful? Give feedback.
-
I will try to get one out but it may take a while. Thanks! |
Beta Was this translation helpful? Give feedback.
-
I know this discussion has moved towards alternatives but to me it seems the underlying cause for this error is being ignored. In the following code, https://github.com/webpack/webpack/blob/main/lib/FileSystemInfo.js#L3029 the code is passing through a null error and result when the upstream filesystem error is ENOENT. Instead of handling this gracefully and providing details of the file in question, the subsequent call stack in _readContextTimestampAndHash.finalize produces an empty object The end result is a cryptic error in a unrelated subsystem rather than a nice clear error that a file wasn't found. Thoughts? |
Beta Was this translation helpful? Give feedback.
-
Just wanted to share my insights here for anyone else who runs into this. For me the issue was the in-memory caching. I had a React application, written in TypeScript, that would fail to recompile when running in the dev server if I didn't save the application entry point file each time I made a change. This was on macOS, mind, but the solution was to set You can browse the exact setup of my project and replicate the issue at this commit. Hope this helps anyone else who runs into this! |
Beta Was this translation helpful? Give feedback.
-
The issue also shows up when there's a problem with reading fileystem information for hashes. In my case it happens with a massively parallelised CI pipeline where |
Beta Was this translation helpful? Give feedback.
-
I encountered the same problem, which is very strange, but I didn't use I used basic |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Bug report
What is the current behavior?
While building the storybook, the process stops with this error.
If the current behavior is a bug, please provide the steps to reproduce.
We upgraded Nrwl Nx from v15.8.6 to v16.3.2. The Nx v15 webpack is 5.75 while the Nx v16 webpack is 5.86
What is the expected behavior?
It should complete the storybookstatic site build by creating in the dist folder the necessary files.
Other relevant information:
webpack version:
5.86.0
Node.js version:
18.15
Operating System:
Windows 11
Beta Was this translation helpful? Give feedback.
All reactions