-
- [ ] vite
- [ ] HTMX
- [ ] leaflet-html
- [ ] linting (prettier, eslint)
- [ ] Storybook
- [ ] testing (vitest)
-
We need a boiler plate package.json files ideally instead of running npm create vite@latest we might be able to just copy the package.json and run npm install.
### Root package
* should include m…
-
#715 has added CI back-end tests execution, but it required adding the Vite manifest because `npm run build` failed in CI.
We should find how to be able to run `npm run build` to generate the Vite ma…
-
### Describe the bug
When running vitest with --coverage using Storybook Test plugin, the reports include story files, which is not expected and affects coverage calculations:
 and want the CSS to be loaded synchronously, but for some reason setting the 2nd argument to false does not work:
````
{{ craft.vite.scrip…
-
### Describe the bug
While debugging a Vitest test case using the VSCode plugin's "Debug Test" functionality, output generated by the test case using `console.log` does not show up in the Test result…
-
### Describe the bug
Thanks so much for creating such wonderful tooling :)
I believe I have found a bug and hope I can describe it well enough here:
* a library project that has @mui/base as a …
ArloL updated
5 hours ago
-
### Describe the bug
Though we know maintaining `cwd` is tricky, can we respect explicit `root` config such as this?
```ts
// packages/client/vite.config.ts
import { defineConfig } from 'vite…
-
### Steps to reproduce
I have a Vite project setup to create lib or module for consumption my Nextjs 14 project. I have one RSC component in my Vite project. Here is source:
```
import { styl…
-
### Describe the bug
I just found a little bug in the typescript for vite.config.ts that when I import BootstrapVueNextResolver with inertia adonisjs or laravel breeze but there are no types availabl…