Jonas Galvez
Jonas Galvez
Interesting — @fastify/vite uses @fastify/middie internally for running Vite development server. And since `@fastify/vite` registers at the global level, there must be a conflict. I'll investigate.
Thanks Manuel, this repo has indeed needed more structure and organization for some time now. - I've opened a [PR to fastify/website](https://github.com/fastify/website/pull/298) to add the book — good call :)...
This is absolutely amazing, thank you @onlywei! I'll be reviewing shortly.
@mcollina Do you see foresee any issues using `node_modules/.cache`?
Can you explain why for instance in TypeScript's case we need `distDir` to be explicit? ```js viteFastify({ distDir: resolve(import.meta.dirname, 'dist') }), ``` Perhaps we should include the explanation as part...
Would checking if `index.html` exists suffice?
I am incredibly swamped at work but will circle back on this over the weekend.
The latest release contains several fixes pertaining `build.outDir` and the use of absolute/relative paths. It also introduces the `distDir` option which can be provided to `@fastify/vite`'s plugin options, matching `build.outDir`.
Vike is Vite-first — Vite controls the entire setup, including the server adapter. `@fastify/vite` is Fastify-first. It also packs a [minimal app shell](https://fastify-vite.dev/vue/project-structure#smart-imports) that allows you have Vue files [register...
Thank you! Indeed, there are few parts which are not covered by HMR. This should be fixed in the next release when I finish the second pass at the Vite...