parcel-bundler / parcel-bundler/lightningcss
Non stable order for keys in CSSModuleExports
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7.7k
- Forks
- 302
- PR merge metrics
- No merged PRs in 30d
Description
You can play with this example: Add and remove new lines at the end of the playground and see the CSS modules output changed.
I need this to be able to better cache the JS file resulting from the CSS modules exports. This is not a big issue, I can easily resort the keys in JS.
Unrelated: Maybe the blue -> #00f transformation should only be applied when minify is on
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 playground example and reproduce how adding or removing trailing newlines changes the CSS modules output. Trace the CSSModuleExports output ordering and determine how to make the keys stable; done means equivalent input changes no longer alter their order. The note about blue becoming #00f is unrelated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, rust
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100