docs: sync latest updates

Author: galvez

docs/.vitepress/theme/styles/base.css

@@ -250,3 +250,17 @@ mjx-container {
 mjx-container > svg {
   margin: auto;
 }
+
+table.roadmap {
+  table-layout: fixed;
+  width: 100%;
+
+}
+
+table.roadmap td:nth-child(2n) {
+  width: 100%;
+}
+
+.release {
+  font-size: 1.2em;
+}

docs/react/index.md

@@ -83,10 +83,9 @@ giget gh:fastify/fastify-vite/starters/react-kitchensink#dev your-app
 
 All dependencies from **react-base**.
 
-
 ## Known limitations
 
-- It's currently impossible to run **multiple** Vite development server middleware in your Fastify server, which means `@fastify/vite` can **only be registered once**.
+- It's currently impossible to run **multiple** Vite development servers, which means `@fastify/vite` can **only be registered once**. Vite's new [Environment API](https://vite.dev/guide/api-environment) was created to avoid this necessity.
 
 - `@fastify/react` currently has no support for producing a fully functional **static bundle**, that is, even when you use [`clientOnly`](/react/rendering-modes#client-only), you'd need to be running the Fastify server integrated with the `@fastify/vite` renderer. SPA support is planned for the next major release, see the [project roadmap](/roadmap).
 

docs/react/project-structure.md

@@ -43,8 +43,6 @@ A `@fastify/react` project must have at the very least:
 
 A Fastify server file that registers `@fastify/vite`.
 
-Or a **plugin** file if running [`fastify-cli`]() or [`platformatic`]().
-
 </td>
 </tr>
 <tr>

docs/react/router-setup.md

@@ -18,7 +18,13 @@ export defaut function MyPage () {
 
 ## Routes location
 
-You can also change the glob pattern used to determine where to route modules from. Internally, this setting is passed to [Vite's glob importer](https://vitejs.dev/guide/features.html#glob-import).
+Internally, the route modules location is set via the `$app/routes.js` [virtual module](/react/project-structure#smart-imports), which is defined as follows by default:
+
+```js
+export default import.meta.glob('/pages/**/*.{jsx,tsx}')
+```
+
+To change the location where routes are loaded from, just place a `routes.js` file at your Vite project's root directory and `@fastify/react/plugin` will automatically recognize it and use it instead.
 
 In your Vite configuration file:
 

docs/roadmap.md

@@ -1,40 +1,50 @@
 # Roadmap
 
 
-<table>
+<table class="roadmap">
 <thead>
 <tr>
-<th>Next releases</th>
+<th>Next majors</th>
 <th>Description</th>
 </tr>
 </thead>
 <tbody>
 <tr>
 <td valign="top">
 
-`@fastify/react`
+<br>
 
-`@fastify/vue`
+<span class="release">
+
+**`@fastify/[email protected]`**
+
+</span>
+
+<br>
 
 <small>
 
 **Target date**
 
 </small>
 
-March 2024
+July 2025
 
 </td>
 <td valign="top">
 
-Planned for the next minor release:
+Planned for this release:
+
+- **Rewrite core in TypeScript**
+- **Deprecate CJS support**
+- **Revised HMR integration**
 
-- Implement Vite's Runtime API.
-- Full hot reload support even without `createRenderFunction()`
+For a long time `@fastify/vite` resisted a TypeScript rewrite, staying true to Fastify's original JavaScript style, which to this date remains CJS written in the same form as seen in Node.js' own internal JavaScript libraries. 
+
+The next major release of `@fastify/vite` will have a TypeScript core and will be compiled to ESM. This release will be coupled with a PR to Fastify itself supporting `import()` Promises in plugin registration calls. 
 
 </td>
 </tr>
+
 </tbody>
 </table>
-
-For **`@fastify/vue`** and **`@fastify/react`**, until the `v1.0.0` release everything can change, and I'd very much like to see [new contributors](/contributing) enhancing the currernt core application shell implemented on those packages and changing what this roadmap looks like in the process!

docs/vue/index.md

@@ -82,7 +82,7 @@ All dependencies from **vue-base**.
 
 ## Known limitations
 
-- It's currently impossible to run **multiple** Vite development server middleware in your Fastify server, which means `@fastify/vite` can **only be registered once**.
+- It's currently impossible to run **multiple** Vite development servers, which means `@fastify/vite` can **only be registered once**. Vite's new [Environment API](https://vite.dev/guide/api-environment) was created to avoid this necessity.
 
 - `@fastify/vue` currently has no support for producing a fully functional **static bundle**, that is, even when you use [`clientOnly`](/vue/rendering-modes#client-only), you'd need to be running the Fastify server integrated with the `@fastify/vite` renderer. SPA support is planned for the next major release, see the [project roadmap](/roadmap).
 

docs/vue/project-structure.md

@@ -43,8 +43,6 @@ A `@fastify/vue` project must have at the very least:
 
 A Fastify server file that registers `@fastify/vite`.
 
-Or a **plugin** file if running [`fastify-cli`]() or [`platformatic`]().
-
 </td>
 </tr>
 <tr>

docs/vue/router-setup.md

@@ -20,21 +20,14 @@ export const path = '/my-page'
 
 ## Routes location
 
-You can also change the glob pattern used to determine where to route modules from. Internally, this setting is passed to [Vite's glob importer](https://vitejs.dev/guide/features.html#glob-import).
-
-In your Vite configuration file:
+Internally, the route modules location is set via the `$app/routes.js` [virtual module](/vue/project-structure#smart-imports), which is defined as follows by default:
 
 ```js
-import viteFastifyVue from '@fastify/vue/plugin'
-
-export default {
-  plugins: [
-    // ...
-    viteFastifyVue({ globPattern: '/views/**/*.vue' }),
-  ]
-}
+export default import.meta.glob('/pages/**/*.vue')
 ```
 
+To change the location where routes are loaded from, just place a `routes.js` file at your Vite project's root directory and `@fastify/vue/plugin` will automatically recognize it and use it instead.
+
 ## Dynamic parameters
 
 Dynamic route parameters uses `[param]` for a singular parameter and `[param+]` for wildcard routes.