-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Build: get rid of webpack
#8314
Conversation
circular dependency still not handle correctly by |
@fisker rollup violate spec in many cases, I do not advertise webpack, but I would advise migrate on webpack in future and avoid rollup |
I normally use I don't have strong opinion, I just try to avoid use two tools. |
@evilebottnawi Out of curiosity, could you tell me how does Rollup violate the spec? |
Bumps [postcss-less](https://github.com/shellscape/postcss-less) from 3.1.4 to 4.0.0. - [Release notes](https://github.com/shellscape/postcss-less/releases) - [Commits](shellscape/postcss-less@v3.1.4...v4.0.0) Signed-off-by: dependabot[bot] <support@github.com>
…-webpack # Conflicts: # package.json # scripts/build/build.js # scripts/build/bundler.js # scripts/build/config.js # yarn.lock
As expected, after upgrade postcss to v8 #9471, we can remove webpack now. |
rollup plugins are very buggy and slow, not sure it is good idea |
# Conflicts: # scripts/build/build.js
We used rollup to bundle all files except Let's remove it and only use |
# Conflicts: # package.json # yarn.lock
Merge after #9482 |
# Conflicts: # package.json # yarn.lock
cacc77e
to
8ca5cb7
Compare
Looks like
postcss
can be bundled byrollup
now.✨Try the playground for this PR✨