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

Support sass 4's @extend SELECTOR, SELECTOR #4088

Closed
DTrejo opened this issue Apr 23, 2020 · 2 comments
Closed

Support sass 4's @extend SELECTOR, SELECTOR #4088

DTrejo opened this issue Apr 23, 2020 · 2 comments

Comments

@DTrejo
Copy link

DTrejo commented Apr 23, 2020

Really enjoying blueprint in our project.

Goal: We'd like to use parcel to import and customize blueprint's CSS. This piece of syntax causes sass 4 to break when it tries to import it. Would it be possible to make it sass 4 compatible? Thanks!

The build error disappeared when I did this:

-@extend .#{$ns}-menu-item:hover;
+@extend .#{$ns}-menu-item, :hover;

@extend .#{$ns}-menu-item:hover;


Full error message

compound selectors may no longer be extended.
Consider `@extend .bp3-menu-item, :hover` instead.
See http://bit.ly/ExtendCompound for details.

╷
19 │ @extend .#{$ns}-menu-item:hover;
│ ^^^^^^^^^^^^^^^^^^^^^^^
╵
node_modules/@blueprintjs/core/src/components/menu/_submenu.scss 19:15 root stylesheet
Error: compound selectors may no longer be extended.
Consider `@extend .bp3-menu-item, :hover` instead.
See http://bit.ly/ExtendCompound for details.

   ╷
19 │       @extend .#{$ns}-menu-item:hover;
   │               ^^^^^^^^^^^^^^^^^^^^^^^
   ╵
  node_modules/@blueprintjs/core/src/components/menu/_submenu.scss 19:15  root stylesheet

Note: I also used this workaround to avoid needing to use svg-icon #2976 (comment)

Note: I also use this .sassrc to support ~ tilde in sass import paths:

{
  "includePaths": [
    "node_modules"
  ]
}
@adidahiya
Copy link
Contributor

looks like a duplicate of #4032. we don't import Blueprint Sass files and customize them in our internal repos, so we haven't hit this bug. I would be open to a bugfix PR as long as it's not a breaking change

@DTrejo
Copy link
Author

DTrejo commented Apr 24, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants