Deprecation warnings when building assets
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 66
- Forks
- 36
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
Describe the bug
We're getting deprecation warnings like Deprecation The legacy JS API is deprecated and will be removed in Dart Sass 2.0.0. when building our assets. This isn't a real problem yet, as assets still get build normally.
To Reproduce
Build the project's assets. The warnings will appear.
Expected behavior
We shouldn't be getting warnings.
Additional context
This seems to be an upstream issue, tracked here (also see here). If this was to be included in a future update of @wordpress/scripts though, we're currently stuck on an old version due to #2624.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the project's asset build and inspect the @wordpress/scripts version constraint discussed in #2624. Compare the warning with the linked Gutenberg upstream reports; done means the build completes without the Dart Sass legacy JS API deprecation warning, subject to an available upstream update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, sass
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100