parcel-bundler / parcel-bundler/lightningcss
Add an option to prevent re-ordering of rules
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7.7k
- Forks
- 302
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
We are using Parcel CSS to bundle our code. Still, we do not want to minify it as we ship it as part of our themes, so they can still be easily edited by agencies, dev, or more importantly our support (we cannot give the original dev files though as the platform we use only allow one CSS).
However, Parcel re-orders every rule, introducing an extra step for our support team as the CSS no longer uses our standard, conventional order. CSS variables end up being scattered randomly in the properties set.
It would be very nice to have an extra option to turn off the re-ordering or eventually turn off the re-ordering when --minify is not set.
Thanks :)
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 by tracing the rule-ordering behavior and the existing handling of the --minify option in Lightning CSS. Define how a new option should affect non-minified output while preserving the intended minification behavior, then verify that CSS rules and custom properties retain their source order when the option is enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100