Skip to content
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

CSS autoprefixes are duplicated #8770

Closed
remino opened this issue Jan 17, 2023 · 2 comments
Closed

CSS autoprefixes are duplicated #8770

remino opened this issue Jan 17, 2023 · 2 comments
Labels

Comments

@remino
Copy link

remino commented Jan 17, 2023

🐛 bug report

When building a CSS file, Parcel adds some compatibility prefixes, but sometimes duplicates them.

Tried both from a Sass file and a plain CSS file.

🎛 Configuration (.babelrc, package.json, cli command)

package.json

{
  "name": "parceltrial2",
  "version": "1.0.0",
  "description": "",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "Rem",
  "license": "ISC",
  "devDependencies": {
    "@parcel/transformer-sass": "^2.8.2"
  }
}

main.sass

body
	backdrop-filter: blur(10px)

Command to build and output

parcel build main.sass && cat build/main.css

main.css

body {
	backdrop-filter: blur(20px);
}

Command to build and output

parcel build main.css && cat build/main.css

🤔 Expected Behavior

The output CSS should only have one -webkit-backdrop-filter:

body{-webkit-backdrop-filter:blur(10px);backdrop-filter:blur(10px)}
/*# sourceMappingURL=main.css.map */

😯 Current Behavior

Each of the two commands stated above produced the same output:

body{-webkit-backdrop-filter:blur(10px);-webkit-backdrop-filter:blur(10px);backdrop-filter:blur(10px)}
/*# sourceMappingURL=main.css.map */

💁 Possible Solution

🔦 Context

Trying to minimize file sizes and redundancy.

💻 Code Sample

See above.

🌍 Your Environment

Software Version(s)
Parcel 2.8.2
Node 18.11.0
npm/Yarn 8.19.2
Operating System macOS Venture 13.0.1
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs.

@github-actions github-actions bot added the Stale Inactive issues label Jul 20, 2023
@github-actions github-actions bot closed this as completed Aug 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants