WordPress.org

Make WordPress Core

Opened 2 months ago

Last modified 6 weeks ago

#51763 new feature request

Evaluate moving to Dart Sass

Reported by: desrosj Owned by:
Milestone: 5.7 Priority: normal
Severity: normal Version:
Component: Build/Test Tools Keywords: needs-patch
Focuses: css Cc:

Description

LibSass and the packages built on top of it (including node-sass) are now deprecated.

They will continue to be maintained indefinitely on a best-effort basis, including fixing major bugs, security issues, and maintaining compatibility with the latest Node versions, but it may be worth looking into converting Core tooling over to Dart Sass, which is the primary implementation of Sass and the recommended replacement.

More information on the decision to deprecate LibSass can be found in the blog post dated October 26, 2020.

Change History (2)

#1 @desrosj
2 months ago

I found out about this deprecation reviewing the PR syncing Twenty Twenty-One to trunk for 5.6 beta 4. The Twenty Twenty-One team made the switch already.

From the blog post:

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. Both packages expose the same JavaScript API.

#2 @desrosj
6 weeks ago

  • Keywords needs-patch added
  • Milestone changed from Awaiting Review to 5.7

This was proposed in GB-22729 and merged into Gutenberg in GB-25628.

Let's tackle this in 5.7 so that this is consistent in both repos.

Note: See TracTickets for help on using tickets.