sass
Better communication about the deprecation
Currently, the readme states that
Warning: LibSass is deprecated. While it will continue to receive maintenance releases indefinitely, there are no plans to add additional features or compatibility with any new CSS or Sass features. Projects that still use it should move onto Dart Sass.
but considering the lack of maintenance with "supported" implementations, this message is not exactly true. From the listed projects:
- ✅ node-sass: Clearly states that the package is deprecated and the repo is archived.
- ❌ perl-libsas: Last commit and release is from two years ago. No deprecation warning.
- ❌ libsass-python: Last release was Jan 2024. Missing wheels for aarch64. No deprecation warning.
- ⚠️ go-libsass: Clear deprecation warning, but the repo is not archived. The last commit is the deprecation warning from 2 years ago.
- ⚠️ sassc-ruby: Clear deprecation warning, but the repo is not archived. The last commit is the deprecation warning from a year ago.
- ❌ libsass-net: No deprecation warning and not maintained anymore. The last commit is from 8 years ago.
- ❌ sass.js: No deprecation warning and not maintained anymore. The last commit is from 6 years ago.
- ⚠️ jsass: No deprecation warning but the repo is archived.
- ❌ sass.ex: No deprecation warning and not maintained anymore. The last commit is from 5 years ago.
- ⚠️ sass_compiler: No deprecation warning but the repo is archived.
Out of 10 packages that listed in the readme, only 3 of those packages have deprecation warnings and only 1 of those 3 uses proper Github features/settings to support that state.
Is it possible to request from their maintainers to share the deprecation warning in their repo? Or, at least, I believe the readme of this repo can be updated to clarify those packages are not maintained anymore and shouldn't be used. All those missing warnings create confusion in their respective communities and I believe that can be solved a pretty small changes in their repos.
To the best of my knowledge there are no plans for any further work on this repository.
Given that, and the multitude of open CVEs, this repository is effectively EOL.
Unless @mgreter has any other plans we should consider archiving this repository. Thoughts @nex3 ?
Given that Marcel hasn't chimed in in the past two weeks (and that this repo hasn't had a commit in two years), I'm on board with officially deprecating LibSass and archiving this repo. I'll prepare a PR for the website.
