sass/dart-sass (sass)
### [`v1.78.0`](https://redirect.github.com/sass/dart-sass/blob/HEAD/CHANGELOG.md#1780)
[Compare Source](https://redirect.github.com/sass/dart-sass/compare/1.77.8...1.78.0)
- The `meta.feature-exists` function is now deprecated. This deprecation is
named `feature-exists`.
- Fix a crash when using `@at-root` without any queries or children in the
indented syntax.
##### JS API
- Backport the deprecation options (`fatalDeprecations`, `futureDeprecations`,
and `silenceDeprecations`) to the legacy JS API. The legacy JS API is itself
deprecated, and you should move off of it if possible, but this will allow
users of bundlers and other tools that are still using the legacy API to
still control deprecation warnings.
- Fix a bug where accessing `SourceSpan.url` would crash when a relative URL was
passed to the Sass API.
##### Embedded Sass
- Explicitly expose a `sass` executable from the `sass-embedded` npm package.
This was intended to be included in 1.63.0, but due to the way
platform-specific dependency executables are installed it did not work as
intended. Now users can run `npx sass` for local installs or just `sass` when
`sass-embedded` is installed globally.
- Add linux-riscv64, linux-musl-riscv64, and android-riscv64 support for the
`sass-embedded` npm package.
- Fix an edge case where the Dart VM could hang when shutting down when requests
were in flight.
- Fix a race condition where the embedded host could fail to shut down if it was
closed around the same time a new compilation was started.
- Fix a bug where parse-time deprecation warnings could not be controlled by
the deprecation options in some circumstances.
Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
â™» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR contains the following updates:
1.77.8->1.78.0Release Notes
sass/dart-sass (sass)
### [`v1.78.0`](https://redirect.github.com/sass/dart-sass/blob/HEAD/CHANGELOG.md#1780) [Compare Source](https://redirect.github.com/sass/dart-sass/compare/1.77.8...1.78.0) - The `meta.feature-exists` function is now deprecated. This deprecation is named `feature-exists`. - Fix a crash when using `@at-root` without any queries or children in the indented syntax. ##### JS API - Backport the deprecation options (`fatalDeprecations`, `futureDeprecations`, and `silenceDeprecations`) to the legacy JS API. The legacy JS API is itself deprecated, and you should move off of it if possible, but this will allow users of bundlers and other tools that are still using the legacy API to still control deprecation warnings. - Fix a bug where accessing `SourceSpan.url` would crash when a relative URL was passed to the Sass API. ##### Embedded Sass - Explicitly expose a `sass` executable from the `sass-embedded` npm package. This was intended to be included in 1.63.0, but due to the way platform-specific dependency executables are installed it did not work as intended. Now users can run `npx sass` for local installs or just `sass` when `sass-embedded` is installed globally. - Add linux-riscv64, linux-musl-riscv64, and android-riscv64 support for the `sass-embedded` npm package. - Fix an edge case where the Dart VM could hang when shutting down when requests were in flight. - Fix a race condition where the embedded host could fail to shut down if it was closed around the same time a new compilation was started. - Fix a bug where parse-time deprecation warnings could not be controlled by the deprecation options in some circumstances.Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
â™» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.