parcel-bundler / parcel-bundler/lightningcss
translate3d after parcel build will change to translate2d
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7.7k
- Forks
- 302
- PR merge metrics
- No merged PRs in 30d
Description
As the title says
when I use parcel build ，code will be compressed and optimize
But something strange and unexpected happened
For example , the css code
transform: translate3d(0, 0, 0) will be optimize and change to transform: translate(0, 0)
I think this operation goes against our original intention
can I know why and Is there a better way to do this than setting up --no-optimize
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 reproducing the reported parcel build optimization with transform: translate3d(0, 0, 0) and trace the CSS optimizer or minifier entry point; no source file or test is named in the issue. Done means the optimization behavior is explained and a regression test or documented result establishes whether the 3D form should be preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, rust
- Domain
- build-system, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100