preset-vite
preset-vite copied to clipboard
preactjs
Preset for using Preact with the vite bundler
This pull request solves #46 by adding `jsxImportSource` to `PreactPluginOptions`. As a bonus, I changed `prepublishOnly` to `prepare`, which allows the package to be installed directly via Git and should...
Adding entries to `optimizeDeps` will prevent these happening and it will reduce start up time. ```text [vite] ✨ new dependencies optimized: preact/debug, preact/jsx-dev-runtime [vite] ✨ optimized dependencies changed. reloading ```...
When using a CSS-in-JS library, aliasing `react` to `preact` may sometimes be insufficient, especially when the library uses its own jsx factory. In my case, I use Emotion, which requires...
### Bug description I am using vite with preact-ts preset. Tried to install a react-specific library (chakra-ui). In development everything is okay, I can see chakra-ui components on the page,...
In my work-in-progress static site renderer @wilsonjs, the prefresh part works, but the devtools part doesn't work at all. My usage of `@preact/preset-vite` is here: https://github.com/wilsonjs/wilson/blob/main/packages/wilson/src/node/vite.ts#L34-L36 Steps to reproduce: -...
### Context: Typical starter preact-ts template with Chakra UI installed. When using the `HStack`, `VStack` or `Stack` components with children nested in them, Vite throws the following error: ``` Uncaught...
I started seeing [this issue](https://github.com/vitejs/vite/issues/8644) after updating vite just now. ``` [vite] hmr update /src/App.tsx [vite] warning: Top-level "this" will be replaced with undefined since this file is an ECMAScript...
If vite is installed with preset-vite in a subdirectory of the project root and both node_modules folders has a preact-lib, there can be a mismatch in which preact-library it should...
Breaking change, don't merge before we're ready! `devtoolsInProd` feels a bit unnecessary, as we can instead toggle based on dev/prod environment (as can the user). If a user wanted to...
It appears that specifying `throwIfNamespace` in a `.babelrc` file no longer causes it to apply to the `@babel/plugin-transform-react-jsx` or `@babel/plugin-transform-react-jsx-development`. Even if specifying `babelrc: true` as a config option. This...
