-
-
Notifications
You must be signed in to change notification settings - Fork 430
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
Heads up: the Sass legacy JS API will start emitting warnings soon #1210
Comments
6 tasks
@alexander-akait I'm not sure that this was resolved by #1211 as that was only meant to change the load order? I can only find a bunch of checks for the |
I see, yeah |
Looks like I was very fast and we need a new major release 😄 |
@alexander-akait I would say "as usual" IMHO 😅☕✌️ |
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Sass team is planning to release a version of Sass soon that begins to emit deprecation warnings for uses of the legacy JS API. Since this is currently the default for Next.js, it might be a good idea to move to using the modern API as the default instead.
The text was updated successfully, but these errors were encountered: