danog/sass-site
1
0
Fork 0
mirror of https://github.com/danog/sass-site.git synced 2024-11-26 20:14:53 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update the timeline for removing @import in the module system blog (#651)

Browse Source
This commit is contained in:
Natalie Weizenbaum 2022-07-06 15:43:20 -07:00 committed by GitHub
parent 652e48b022
commit faf93b9cb7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 13 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
source/blog/024-the-module-system-is-launched.html.md
View File

@ -337,15 +337,22 @@ However, doing away with `@import` entirely is the ultimate goal for simplicity,
performance, and CSS compatibility. As such, we plan to gradually turn down
support for `@import` on the following timeline:
- One year after both Dart Sass and LibSass have launched support for the
- ~~One year after both Dart Sass and LibSass have launched support for the
module system _or_ two years after Dart Sass launches support for the module
system, whichever comes sooner (**1 October 2021** at latest), we will
deprecate `@import` as well as global core library function calls that could
be made through modules.
be made through modules.~~
- One year after this deprecation goes into effect (**1 October 2022** at
- ~~One year after this deprecation goes into effect (**1 October 2022** at
latest), we will drop support for `@import` and most global functions
entirely. This will involve a major version release for all implementations.
entirely. This will involve a major version release for all implementations.~~
This means that there will be at least two full years when `@import` and `@use`
are both usable at once, and likely closer to three years in practice.
~~This means that there will be at least two full years when `@import` and `@use`
are both usable at once, and likely closer to three years in practice.~~
**July 2022**: In light of the fact that LibSass was deprecated before ever
adding support for the new module system, the timeline for deprecating and
removing `@import` has been pushed back. We now intend to wait until 80% of
users are using Dart Sass (measured by npm downloads) before deprecating
`@import`, and wait at least a year after that and likely more before removing
it entirely.