parcel-bundler / parcel-bundler/lightningcss
support an option to keep invalid css in the output
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7.7k
- Forks
- 302
- PR merge metrics
- No merged PRs in 30d
Description
This is a follow up issue of https://github.com/parcel-bundler/lightningcss/issues/209 and thank you support errorRecovery to make migration from postcss to lightningcss much easier.
But there's still a pain point that user might still want to keep the invalid css to leave it processed by other tools, so it may make sense to support an option to keep the invalid css in the output, we met some problem when use lightningcss in rspack related to this
- https://github.com/web-infra-dev/rspack/issues/8695#issuecomment-2540704499
- https://github.com/web-infra-dev/rspack/issues/10056
also seems related issue in turbopack
Discussed similar problem with webpack and esbuild author about how to deal with invalid css in https://github.com/evanw/esbuild/issues/1946#issuecomment-1017203765 and it seems keep invalid css may make sense.
Again Thanks for your great work!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked follow-up issue 209 and the existing errorRecovery behavior, then review pull request 954 and the referenced Rspack, Turbopack, Webpack, and esbuild discussions. Done means defining and implementing an option that preserves invalid CSS in the output while allowing other processing to continue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100