Backport deprecation API to legacy JS API#3907
Merged
Conversation
b6fbe0b to
69dcac9
Compare
This was referenced Jul 29, 2024
nex3
approved these changes
Jul 30, 2024
nex3
approved these changes
Aug 22, 2024
Contributor
There was a problem hiding this comment.
For the specs, I think it's fine to just link to the non-legacy API definitions rather than writing them out again.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a fast-track proposal to backport the deprecation options to work in the legacy JS API. Some bundlers don't support the modern API, so adding these options to the legacy API allows users of those bundlers to still control their deprecation warnings.
The behavior of each option in the legacy API matches its behavior in the modern API (the text here is directly copied from the modern API spec).
[skip dart-sass]
[skip sass-embedded]