VS Code and/or linting

[mindplay-dk]

How is everyone dealing with IDE support in VS Code and/or linting?

We've been relying on vscode-styled-components, but this was dead by June 2024, before Styled Components itself pulled the plug.

By now, our devs are adopting things like @container in CSS, and the legacy extension can't parse this syntax, and also rejects all the new CSS properties that come with containers.

So at the moment you can choose between a long list of false positives, with actual errors drowning out in the noise - or disabling the extension and coding with no IDE support.

Someone highlighted the issue in an older thread (which should probably just be closed) but there was no reaction to that, so I'm starting a dedicated thread.

Is anything on the roadmap for this?

We moved a huge project from Styled Components to Emotion last summer - I know the CSS-in-JS climate isn't great for the style components approach, but our team likes it, and we were hoping this project would carry the torch. 🙂

I wish I could help, but I've never worked on a VS Code extension myself.

If there are no plans to build an official fork of this extension (or start something new) I might take a stab at it and fumble around with LLMs to see if I can bring it back from the dead. 😊

[SamuelRnn]

I was thinking in creating my own solution to this very common unattended issue. Seems like there's no official plans on upgrading the support for the extension. Having the same problem doing a migration for my team's project.