New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vite compatibility? #26
Comments
Seems like Vite supports Babel: Through babel-plugin-macros. |
The babel plugin doesn't do fancy CSS extraction. But tamagui is nicely sorted into packages, so actually the webpack loader mostly shares code nicely with babel plugin for example. It should be well set up to try and adapt to Vite if they do have a plugin system for extracting CSS. |
Seems like Vite already extracts CSS without a plugin:
With respect to SSR, maybe this can help: Vite.js & Rollup plugin for generating critical (above-the-fold) CSS: What do you think? |
If someone starts PR happy to help, probably wont prioritize for a while. |
@redbar0n Are you working on it or planning to do? If not I'm consindering trying to implement it. But it might take a while until I find the time to do it. |
@jsfroth no, I don’t have the capacity at the moment. It’d be awesome if you would start a branch and invite people to join in the work on it. |
FWIW, I’m also keeping an eye on Bun as an alternative to Vite: https://betterprogramming.pub/is-bun-the-next-big-thing-after-webpack-d683441f77b9 There’s quite a bit of development in the field these days. NextJS (Vercel) having hired the Webpack maintainer, presumably to improve performance, as well. |
I got basic support with Vite, but without static extraction: See this config for reference: https://github.com/tamagui/tamagui/blob/master/packages/sandbox/vite.config.ts Closing this, I'll get to the extraction plugin sometime soon. |
tsc
), and uses Rollup for production builds.I’d like to use Tamagui with vite-plugin-ssr instead of NextJS (which is tied to Webpack…).
I see that you use Webpack and Babel currently.
The text was updated successfully, but these errors were encountered: