Skip to content

DEPRECATION WARNING: The legacy JS API is deprecated and will be removed in Dart Sass 2.0.0. #656

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

Closed
Keavon opened this issue Sep 23, 2024 · 2 comments · Fixed by #657
Closed

Comments

@Keavon
Copy link

Keavon commented Sep 23, 2024

Describe the bug
According to:

> npm ls sass
my-project
├─┬ [email protected]
│ └── [email protected]
└─┬ [email protected]
  └── [email protected] deduped

This, together with Vite, both pull in Sass 1.79 which has begun spamming the console with deprecation warnings (see Logs in the next paragraph). Vite already has an issue open for this, but I'm creating one here as well. They opted to downgrade to Sass 1.78 and that might be a viable solution here too.

Logs
The following is spammed repeatedly to the console:

More info: https://sass-lang.com/d/legacy-js-api

DEPRECATION WARNING: The legacy JS API is deprecated and will be removed in Dart Sass 2.0.0.

To Reproduce
Use Sass in your Svelte 4 project and bundle it with Vite.

Expected behavior
No console spam.

Information about your project:

I'm running Windows 11 and here is my package.json. The problem occurs when all dependencies are fully up-to-date, but I'm avoiding upgrading for now until this issue is resolved.

dummdidumm added a commit that referenced this issue Sep 26, 2024
Quick fix for now, in the mid term we should add proper support for the new API

fixes #656
@kaisermann
Copy link
Member

@Keavon

Vite already has an issue open for this, https://reddit.com/r/opensource/comments/1fk4jot/whats_some_super_beautiful_open_source_uis, but I'm creating one here as well. They opted to downgrade to Sass 1.78 and that might be a viable solution here too.

I think you pasted the wrong link 😅

@Keavon
Copy link
Author

Keavon commented Sep 26, 2024

Indeed, I'm not sure how I didn't notice that was the wrong paste 🤔

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 a pull request may close this issue.

2 participants