-
Notifications
You must be signed in to change notification settings - Fork 74
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
💣🐒 Reduce webpackers' config monkey-patching and use v5 default #3275
Conversation
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.
Some questions and nitpicks that you may or may not ignore, at your discretion. This is a huge improvement!
bdb2866
to
ed7d216
Compare
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.
another nit pick but looks good!
cde9c2b
to
5d5e5ef
Compare
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.
Why not upgrading @types/jest
? Does it do any harm?
0032fd5
to
beb06fe
Compare
It's not directly related to webpacker and I'd like to upgrade the whole jest suite in another PR. |
beb06fe
to
5165d48
Compare
885909a
to
04e6976
Compare
a3bffcc
to
511974f
Compare
This is not looking good. CI won't compile because OOM, the bundle is bigger and styles are not injected causing some tests to fail. |
Ran
webpacker install
to "re-install" all default files and configs and then cleaned up everything so that we have a standard webpacker installation. This way the upgrade to v6 and later shakapacker will happen smoothly.