Skip to content

Prefer sass over node-sass #870

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

Merged
merged 1 commit into from
Dec 3, 2020
Merged

Conversation

weaverryan
Copy link
Member

This will change the recommendation to sass instead of node-sass which is deprecated and harder to deal with. I haven't had any issues or differences working with sass yet vs node-sass.

I also upgraded the lock file in general, it makes it easier to see what packages are legitimately out of date and doesn't affect end users.

@weaverryan weaverryan merged commit eb559f0 into symfony:main Dec 3, 2020
@weaverryan weaverryan deleted the prefer-sass branch December 3, 2020 16:39
@Kocal
Copy link
Member

Kocal commented Dec 3, 2020

I haven't had any issues or differences working with sass yet vs node-sass.

I faced one issue which is related to vue-loader, if you use scoped styles and still want to style a deeper element, you can use >>> (CSS) or /deep/ (node-sass) or ::v-deep (dart sass). /deep won't work on Dart Sass because of syntax error.

@stof
Copy link
Member

stof commented Dec 3, 2020

yeah, that's because the /deep/ proposal has been rejected in the CSS spec and so has been removed from the sass syntax as well in dart-sass (ruby-sass was warning about it being deprecated and libsass had a todo about implementing the deprecation IIRC)

wouterj added a commit to symfony/symfony-docs that referenced this pull request Dec 5, 2020
This PR was submitted for the 5.2 branch but it was merged into the 4.4 branch instead.

Discussion
----------

Prefer sass over node-sass

Hi!

`node-sass` is deprecated in favor of `sass` - https://sass-lang.com/blog/libsass-is-deprecated.  Encore works exactly the same with both, and `sass` doesn't require an annoying compile step that sometimes fails anyways.

And also, here is the PR that will change which library is recommended: symfony/webpack-encore#870

I will merge and tag that shortly.

Commits
-------

41418b7 Prefer sass over node-sass
pfz pushed a commit to pfz/webpack-encore that referenced this pull request Dec 14, 2020
This PR was merged into the main branch.

Discussion
----------

Prefer sass over node-sass

This will change the recommendation to `sass` instead of `node-sass` which is deprecated and harder to deal with. I haven't had any issues or differences working with `sass` yet vs `node-sass`.

I also upgraded the lock file in general, it makes it easier to see what packages are legitimately out of date and doesn't affect end users.

Commits
-------

aec475d prefer sass over node-sass
pfz pushed a commit to pfz/webpack-encore that referenced this pull request Dec 14, 2020
This PR was merged into the main branch.

Discussion
----------

Prefer sass over node-sass

This will change the recommendation to `sass` instead of `node-sass` which is deprecated and harder to deal with. I haven't had any issues or differences working with `sass` yet vs `node-sass`.

I also upgraded the lock file in general, it makes it easier to see what packages are legitimately out of date and doesn't affect end users.

Commits
-------

aec475d prefer sass over node-sass
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants