Add type-safety for classnames in vs code

[siddharthkp]

Added type-safety for classnames with typescript-plugin-css-modules in the editor.

Unfortunately, tsc doesn't load plugins yet, so we don't get typechecks for classnames in CI and are stuck with declaring loose definitions in global.d.ts for now.

---

Note: Make sure your editor is using the workspace version of typescript to use the plugin. See typescript docs

[changeset-bot]

⚠️ No Changeset found

Latest commit: 42be9b1

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[joshblack]

Very cool! 🥳 For the type error, do we need something like: https://www.npmjs.com/package/typescript-plugin-css-modules#user-content-custom-definitions or is what you had before in global.d.ts good to use? 👀

[siddharthkp]

Very cool! 🥳 For the type error, do we need something like: https://www.npmjs.com/package/typescript-plugin-css-modules#user-content-custom-definitions or is what you had before in global.d.ts good to use? 👀

We do :( (updated)

I was hoping we wouldn't need it, only to realise tsc doesn't load plugins

[github-actions]

size-limit report 📦

Path	Size
dist/browser.esm.js	101.63 KB (0%)
dist/browser.umd.js	102.18 KB (0%)