Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

using of .sassrc.js messes sass output with multiple entry points #1280

Closed
safareli opened this issue May 3, 2018 · 2 comments
Closed

using of .sassrc.js messes sass output with multiple entry points #1280

safareli opened this issue May 3, 2018 · 2 comments
Labels
🐛 Bug Stale Inactive issues

Comments

@safareli
Copy link

safareli commented May 3, 2018

This a 🐛 bug report.

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

index.html

 index.html
<html>
<head>
  <link href='A.scss' rel='stylesheet' />
  <link href='B.scss' rel='stylesheet' />
</head>
<body>
  hi
</body>
</html>

package.json

{
  "name": "parcel-test",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "node-sass": "^4.9.0",
    "parcel-bundler": "^1.7.1"
  }
}

.sassrc.js

module.exports = {};

A.scss

.A { color: black }

B.scss

.B { color: blue }

🤔 Expected Behavior

dist/A.css

.A {
  color: black }

dist/B.css

.B {
  color: blue }

😯 Current Behavior

dist/A.css

.A {
  color: black; }

dist/B.css

.A {
  color: black; }

.B {
  color: blue; }

here is somewhat full dump of the test case https://gist.github.com/safareli/8200eccaa6f3a90cf9888a1d2a5bee1b

Issue is that dist/B.css contains contents of A.scss. If you remove .sassrc.js or use .sassrc with {} as contents then the issue is not present. Why do I need .sassrc.js instead of .sassrc? as it's the way to depend on staff from node_modules or bower_components etc.. see #39 (comment)

@safareli
Copy link
Author

safareli commented May 4, 2018

another issue with .sassrc.js #1291

@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.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
🐛 Bug Stale Inactive issues
Projects
None yet
Development

No branches or pull requests

2 participants