Skip to content
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

webpack 5 support #6081

Closed
crobinson42 opened this issue Dec 21, 2018 · 8 comments
Closed

webpack 5 support #6081

crobinson42 opened this issue Dec 21, 2018 · 8 comments
Labels

Comments

@crobinson42
Copy link

Webpack v5 is coming down the pipeline with some awesome improvements - is there any discussions or plans to get this in CRA when the major drops?

@crobinson42
Copy link
Author

@bugzpodder
Copy link

We can look into it once it gets to beta/stable. It would also be a major version bump to cra (3.0).

@mrmckeb
Copy link
Contributor

mrmckeb commented Dec 22, 2018

@bugzpodder - would it need a major bump? It's obviously not ready for us to use yet, but if there are no breaking changes for our end users, we could probably release as a 2.x version?

@bugzpodder
Copy link

Yep that sounds good. I forgot that CRA already dropped support for Node 6, so it should be less of a problem.

@stale
Copy link

stale bot commented Jan 22, 2019

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.

@itsmelion
Copy link

After CRA shifted to 2.x its deps are ok in keeping up-to-date.
For me, that's really important, and since then i stopped ejecting projects because of that.
Deps to keep a close eye on are especially: Webpack and its loaders, PostCSS, and Babel.

@stale
Copy link

stale bot commented Mar 11, 2019

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.

@stale stale bot added the stale label Mar 11, 2019
@stale
Copy link

stale bot commented Mar 16, 2019

This issue has been automatically closed because it has not had any recent activity. If you have a question or comment, please open a new issue.

@stale stale bot closed this as completed Mar 16, 2019
@lock lock bot locked and limited conversation to collaborators Mar 21, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants