-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] Webpack@5 #46
[WIP] Webpack@5 #46
Conversation
lint and test are failing can you check? can you also list any issues of loaders to support webpack 5? good job |
is it faster on first build? |
Tests are failing trying to load a Now apparently webpack build stopped working and i have no idea why. I'm looking at it and also i'm still looking at those plugins that need to be updated. |
the first run was 2000ms I nice improvement over the cache I've got this problem https://github.com/shellscape/webpack-plugin-serve/blob/master/.github/FAQ.md#what-does-the-not-found--404-error-mean maybe it is related to html-webpack-plugin we can remove mini css, as we use styled-components, no need for directly css |
wps hmr client file is not being generated as well |
it is also not generating .cache directory |
Migrating html-webpack-plugin to 4 beta5 solves the problem with it but it throws another error Uncaught ReferenceError: global is not defined
at eval (index.js?e792:25)
at Object../node_modules/@babel/polyfill/lib/index.js (bundle.js:3822)
at __webpack_require__ (bundle.js:24)
at fn (bundle.js:4146)
at eval (index.tsx:2)
at Module../src/index.tsx (bundle.js:3951)
at __webpack_require__ (bundle.js:24)
at startup (bundle.js:46)
at bundle.js:53
at bundle.js:56 |
…a5 to work nice with wp5
maybe related to webpack/webpack#8537 (comment) |
Interesting that it changed... I'm going to investigate if the behavior I was getting yesterday continues even with the beta version. Because not even with a python server the bundle was being executed (on web) |
Yeah, apparently it is related. They moved the builtins to a runtime plugin, which apparently isn't working properly anymore... i'm going to track that down |
On normal builds, without a dev-server, it went from: 4s on first build to 2s on next builds. |
Fixed, but
Feedback left here: jantimon/html-webpack-plugin#1129 |
not ready yet |
Codecov Report
@@ Coverage Diff @@
## master #46 +/- ##
=========================================
Coverage ? 82.23%
=========================================
Files ? 21
Lines ? 197
Branches ? 35
=========================================
Hits ? 162
Misses ? 27
Partials ? 8
Continue to review full report at Codecov.
|
"@types/react-relay": "1.3.10", | ||
"@types/rebass": "0.3.4", | ||
"@types/styled-components": "4.1.6", | ||
"@types/styled-system": "3.1.3", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can move all @types to root package
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Even if types are not "common"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let them here then
we can try again next week, tks |
per #43 .
I reworked some files, moved some dependencies to the top level and updated some. Server still having issues to start due to what was already reported on #42.
It is a WIP, i still need to find a better way to clean cache when we change any webpack config. I'm gonna read the changelog and see what they suggest.
Otherwise, it's pretty complete i guess.
ps: some plugins/loaders on web package i had to comment it out, they are not ready to be moved to webpack5 yet (yeah, more breaking changes).
The following plugins are broken:
mini-css-extract-plugin
html-webpack-plugin