Please remove [IN PROGRESS] from "CSS as first-class citizen"
glen-84 opened this issue · comments
It doesn't seem to be in progress anymore, and I'd like to be able to vote on it.
It would also be nice to have "HTML as first-class citizen" and "Files/assets/URLs as first-class citizen".
@glen-84 it is in progress for webpack@5, just no priority
It may be planned for webpack 5 (although it's not even on the project page?), but as far as I can tell, it's certainly not in progress.
@glen-84 feel free to send a PR
Where is the data stored?
I believe it’s stored somewhere in AWS, managed by @sokra or @TheLarkInn. You can see the REST calls we make for the data here:
https://github.com/webpack-contrib/voting-app/blob/master/src/utils/js/api.js
I guess I can't send a PR then.
True but you could reach out to them and ask nicely
- [short term] Can one of you make the update to the above-mentioned vote item?
- [long term] Maybe there's a better way to expose this data? Since the amount of data is minimal it could be exposed in this repo instead which would allow people to PR changes with your review.
As for the second point, idk the rationale behind it being stored in AWS in the first place so I could definitely be missing a valid concern.
I updated it.
It need to have a backend to allow voting. Technically it's possible to put the info into github, but it also works great this way.
I can vote now (thanks), but the title still includes [IN PROGRESS].
Also, is there any chance that we could get "HTML as first-class citizen" and "Files/URLs as first-class citizen"?
sure, added.
I can vote now (thanks), but the title still includes
[IN PROGRESS].
yep, because we already have worked towards this.
sure, added.
Awesome! Thanks a lot.
yep, because we already have worked towards this.
The infrastructure for module types in general, or something specific to CSS? (or the work related to the mini-css-extract-plugin?)
"In progress" generally means "currently happening", but anyway I'm just happy that I'm able to vote for it now.
Thanks for the work that you do.
The infrastructure for module types in general, or something specific to CSS? (or the work related to the mini-css-extract-plugin?)
with webpack 4 and the mini-css-extract-plugin, CSS is already a module type, which has a lot of benefits (like code-splitting).
webpack 5 will add the ability to support HMR for other module types and MCEP will be improved towards this.
I'm looking forward to the day that MCEP is not even required. HTML and CSS entry points will make working with non-JS modules so much easier and more logical.
webpack/webpack#536 has the most