One concern with the current maintenance state of the VS Code CSS language extension is that newer CSS functionality and standards support do not appear to be implemented in a timely manner.
Because this extension is built into VS Code and effectively serves as the default CSS language experience for a huge number of developers, missing support for modern CSS features has a significant downstream impact.
Examples include newer CSS specifications and syntax additions that are already supported in browsers but still lack proper tooling support in VS Code.
The issue is less about “new features” and more about long-term standards maintenance and ecosystem reliability.
Could maintainers look into handing over the maintenance to someone more active, that take active responsibility for this repo?
This repo has effectively been abandoned by Microsoft, see:
https://github.com/microsoft/vscode-css/graphs/contributors?from=5%2F25%2F2024
One concern with the current maintenance state of the VS Code CSS language extension is that newer CSS functionality and standards support do not appear to be implemented in a timely manner.
Because this extension is built into VS Code and effectively serves as the default CSS language experience for a huge number of developers, missing support for modern CSS features has a significant downstream impact.
Examples include newer CSS specifications and syntax additions that are already supported in browsers but still lack proper tooling support in VS Code.
The issue is less about “new features” and more about long-term standards maintenance and ecosystem reliability.
Could maintainers look into handing over the maintenance to someone more active, that take active responsibility for this repo?
This repo has effectively been abandoned by Microsoft, see:
https://github.com/microsoft/vscode-css/graphs/contributors?from=5%2F25%2F2024