Dmytro Z.

Results 86 comments of Dmytro Z.

Here is the minimal project to repro this issue: [https://github.com/zdm/webpack-bundle-analyzer-issue-471](https://github.com/zdm/webpack-bundle-analyzer-issue-471) ``` npm i npx webpack-dev-server ``` See errors: ``` ... Error parsing bundle asset "d:\downloads\webpack-bundle-analyzer-issue-471\www\js\vendors.1989a8af.js": no such file Error parsing...

I updated code to use path.resolve. Results are the same. On 02.10.2021 19:06, Alexander Akait wrote: > |path.resolve(__dirname, '/www')|

Under linux results are the same too. The problem is not in the paths separators.

This can be problematic for me because I am not in the context of this project. I can help in testing. Will wait, no other way...

Did you solved this problem? I have similar case.

I am not a native English carrier, and always forget the difference between must and should. Sorry, if it was offensive for you. Obvious, that if the content wasn't updated...

So, what is the decision? Let's close this issue if code will stay as is.

When you will update dependencies? It NOT works with visual studio 2022 on github actions.

All you need to do is to change `"node-gyp": "^6.0.1"` to `"node-gyp": "^8.0.0"` in `package.json`. API interface not changed and it just works.