-
-
Notifications
You must be signed in to change notification settings - Fork 372
Migrate to webpack v4 #502
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
Conversation
@mertkahyaoglu I just can't seem to get ESLint to accept properties in ES6 classes. Any suggestions..? |
Hi @mertkahyaoglu |
@lexoyo I suspect the issue is probably with |
I couldn't have a chance to look into this. Gonna investigate the issue today. We can try bumping |
Thank you for looking into this, @lexoyo and @mertkahyaoglu. You guys were correct. The outdated versions of There are some warnings and errors in the Travis log, but the production build completes successfully locally.. |
Flushed the build caches at Travis to induce creation of fresh bindings for Remaining TODO:
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@mertkahyaoglu I don't know what more is left to reduce the log output from webpack in dev mode. |
Bundle size comparison (across AppVeyor builds):
|
webpack 5 is around the corner.
Migrating to v4 now will ease the future migration.