add TS support, cleans up modules

[argyleink]

fixes #333

microbundle wasnt building friendly files, making them hard to infer types from and impossible for authors to read. this drastically simplifies the build output for js modules while also adding a .ts file and .d.ts typings file.

preview of open-props.ts:

export default {
  "--animation-fade-in": "fade-in .5s var(--ease-3)",
  "--animation-fade-in-@": "\n@keyframes fade-in {\n  to { opacity: 1 }\n}",
  "--animation-fade-in-bloom": "fade-in-bloom 2s var(--ease-3)",
  ...
}

preview of open-props.d.ts:

declare const OpenProps: {
  "--animation-fade-in": "string";
  "--animation-fade-in-@": "string";
  "--animation-fade-in-bloom": "string";
  "--animation-fade-in-bloom-@": "string";
  ...
}

thoughts @mayank99 or @hchiam?

no new deps, no invasive or fancy ts; just an easier to infer dist file for TS to grab

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[github-actions]

Visit the preview URL for this PR (updated for commit 6505111):

https://open-props--pr335-ts-autocomplete-j2g6ul5x.web.app

_{(expires Tue, 31 Jan 2023 01:41:04 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: 32524ac481f54edda55dc959fa4614cf1acc8c11}

[mayank99]

so now there will be typings for the default export from root, but not for any additional paths. is the goal to stop here or to allow a separate PR to generate those additional DTS files?

[hchiam]

i've got nothing to add beyond @mayank99's comment #335 (comment)
LGTM! 👍

[argyleink]

but not for any additional paths. is the goal to stop here or to allow a separate PR to generate those additional DTS files?

i was going to stop here, but it's not much more effort to produce individual .d.ts files now the system is laid out. it'd be good to have parity in the import syntax, just so the docs can stay clean and dont diverge 👍🏻 aka, assume i'll add to this PR

[argyleink]

[argyleink]

alright y'all, i'll merge this tomorrow if we're feelin good about it. thanks for everyones help and effort!

[argyleink]

oh! or i need to figure out why the test failed first 🙂

[argyleink]

super glad y'all're makin suggestions so we can collab on this PR 🙂
i'm also at home with kids hehe, they came home right when i was accepting the first round of suggestions

[mayank99]

yo, you said tomorrow. i was just in the process of testing this with npm pack + local apps lol

no worries, i'll test with actual 1.5.4

[argyleink]

ah, sorry! i did. it just seemed ready and done.

i updated https://stackblitz.com/edit/react-vanillaextract-openprops to latest and typeahead was there. how'd it go for you? all good? new gitignore got em all?