question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Deprecation of node-sass

See original GitHub issue

Where to find the issue

https://github.com/corona-warn-app/cwa-website/blob/master/package.json https://github.com/corona-warn-app/cwa-website/blob/master/gulpfile.js

Describe the issue

According to https://www.npmjs.com/package/node-sass “Node Sass” used by cwa-website is deprecated:

“Warning: LibSass and Node Sass are deprecated. While they will continue to receive maintenance releases indefinitely, there are no plans to add additional features or compatibility with any new CSS or Sass features. Projects that still use it should move onto Dart Sass.”

Suggested change

Migrate from node sass to Dart Sass see https://sass-lang.com/blog/libsass-is-deprecated which says:

“If you’re a user of Node Sass, migrating to Dart Sass is straightforward: just replace node-sass in your package.json file with sass.”

however the change is not quite so simple. To remediate Deprecation Warning: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0. More info and automated migrator: https://sass-lang.com/d/slash-div it is necessary to run the migrator.

  1. npm uninstall node-sass
  2. npm install sass@latest
  3. Replace node-sass by sass in gulpfile.js
  4. npm install -g sass-migrator
  5. sass-migrator division **/*.scss

Internal Tracking ID: EXPOSUREAPP-14243

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:5 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
svengabrcommented, Feb 7, 2022

Not having any intentions of migrating for the moment so this issue will be closed.

1reaction
MikeMcC399commented, Feb 7, 2022

@svengabr I agree that @Ein-Tim said it was only a temporary testing issue which he has now resolved. As far as I can see everything is working and there is no urgent need to make any changes in this respect.

If you think that addressing the deprecation of node-sass by migrating to sass is something which might soon be done, then I suggest to leave this issue open as a reminder.

If there are no near-term plans to do this, then I suggest closing the issue.

Read more comments on GitHub >

github_iconTop Results From Across the Web

'node-sass' usage is deprecated and will be removed in a ...
'node-sass' usage is deprecated and will be removed in a future major version. To opt-out of the deprecated behaviour and start using 'sass' ......
Read more >
LibSass is Deprecated - Sass
LibSass and Node Sass will continue to be maintained indefinitely on a best-effort basis, including fixing major bugs and security issues and ...
Read more >
sass/node-sass: Node.js bindings to libsass - GitHub
Warning: LibSass and Node Sass are deprecated. While they will continue to receive maintenance releases indefinitely, there are no plans to add additional ......
Read more >
node-sass - npm
Start using node-sass in your project by running `npm i node-sass`. There are 12491 other projects in the npm registry using node-sass.
Read more >
Migrating from Node-Sass to Sass (Dart-Sass) with npm
For 2 years now, LibSass and node-sass has been deprecated. A lot of reasons led the core team to this decision.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found