Closed Saiv46 closed 2 years ago
Module not found: Error: Can't resolve 'tls' in '/home/runner/work/prismarine-web-client/prismarine-web-client/node_modules/https-proxy-agent/dist'
The fuck? How my PRs breaking other webpack plugins in unexpected ways?
I fixed the tls issue
@KalmeMarq @AwesomestCode can you check if this works for you?
Things that should work:
this will get closed in 5 days if nobody tests it
Tested with latest webpack
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "url": require.resolve("url/") }'
- install 'url'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "url": false }
@ ./node_modules/.pnpm/github.com+PrismarineJS+net-browserify@0acebf76d5a_5678e2fd34bc6a9aacd7b63820e4e40f/node_modules/net-browserify/browser.js 4:11-26
@ ./index.js 11:12-26
I still can't get build work with PNPM, while NPM installing packages slower on my new SSD
Quickly checked npm start
on GitPod. It compiles successfully though some assets seem to be missing? Or my computer might just be weird.
Edit: also tested on my Chromebook. Same issue, happens with npm run build-start
too.
Confirmed that the issue does not happen on master
.
Closed in favor of #253
It uses modified time of source and destination files (if exists) to filter out unchanged files from being copied on build.
Closes #210