diff --git a/boilerplates/boilerplate-react-ts/package.json b/boilerplates/boilerplate-react-ts/package.json index b6c4c0010e2..985d62b251e 100644 --- a/boilerplates/boilerplate-react-ts/package.json +++ b/boilerplates/boilerplate-react-ts/package.json @@ -2,7 +2,7 @@ "scripts": { "dev": "npm run server:dev", "prod": "npm run build && npm run server:prod", - "build": "vite build", + "build": "vike build", "server": "node --loader ts-node/esm ./server/index.ts", "server:dev": "npm run server", "server:prod": "cross-env NODE_ENV=production npm run server" diff --git a/boilerplates/boilerplate-react/package.json b/boilerplates/boilerplate-react/package.json index 33f8daadae4..4560c6c347e 100644 --- a/boilerplates/boilerplate-react/package.json +++ b/boilerplates/boilerplate-react/package.json @@ -2,7 +2,7 @@ "scripts": { "dev": "npm run server:dev", "prod": "npm run build && npm run server:prod", - "build": "vite build", + "build": "vike build", "server:dev": "node ./server", "server:prod": "cross-env NODE_ENV=production node ./server" }, diff --git a/boilerplates/boilerplate-vue-ts/package.json b/boilerplates/boilerplate-vue-ts/package.json index 81b1b7c91df..68f01426f15 100644 --- a/boilerplates/boilerplate-vue-ts/package.json +++ b/boilerplates/boilerplate-vue-ts/package.json @@ -2,7 +2,7 @@ "scripts": { "dev": "npm run server:dev", "prod": "npm run build && npm run server:prod", - "build": "vite build", + "build": "vike build", "server": "node --loader ts-node/esm ./server/index.ts", "server:dev": "npm run server", "server:prod": "cross-env NODE_ENV=production npm run server" diff --git a/boilerplates/boilerplate-vue/package.json b/boilerplates/boilerplate-vue/package.json index 3854da713fc..82f75abbc0c 100644 --- a/boilerplates/boilerplate-vue/package.json +++ b/boilerplates/boilerplate-vue/package.json @@ -2,7 +2,7 @@ "scripts": { "dev": "npm run server:dev", "prod": "npm run build && npm run server:prod", - "build": "vite build", + "build": "vike build", "server:dev": "node ./server", "server:prod": "cross-env NODE_ENV=production node ./server" }, diff --git a/docs/components/static-host.tsx b/docs/components/static-host.tsx index 26eb8bdda7c..ad09f10d8de 100644 --- a/docs/components/static-host.tsx +++ b/docs/components/static-host.tsx @@ -40,7 +40,7 @@ function StaticHostDocStrategies({ name = 'the static host' }: { name?: string }
> @@ -53,7 +53,7 @@ function StaticHostDocOutro({ baseUrlAddendum }: { baseUrlAddendum?: React.JSX.E {' '} You can try out your production build locally with{' '} -- The
$ vite build
command generatesdist/client/
containing all static assets. + The$ vike build
command generatesdist/client/
containing all static assets.
$ vite preview
+ $ vike preview
, or any other tool such as{' '}
diff --git a/docs/headings.ts b/docs/headings.ts
index 18f1580f6f6..8972032c90a 100644
--- a/docs/headings.ts
+++ b/docs/headings.ts
@@ -337,6 +337,16 @@ const headings = [
url: '/config',
sectionTitles: ['`+` files']
},
+ {
+ level: 2,
+ title: 'CLI',
+ url: '/cli'
+ },
+ {
+ level: 2,
+ title: 'JavaScript API',
+ url: '/api'
+ },
{
level: 2,
title: 'Error Page',
diff --git a/docs/headingsDetached.ts b/docs/headingsDetached.ts
index 9347442024c..6c8ede8f9d5 100644
--- a/docs/headingsDetached.ts
+++ b/docs/headingsDetached.ts
@@ -321,6 +321,10 @@ const headingsDetached: HeadingDetachedDefinition[] = [
title: '`useClientRouter()`',
url: '/useClientRouter'
},
+ {
+ title: 'CLI Migration',
+ url: '/migration/cli'
+ },
{
title: 'Migration `0.4`',
url: '/migration-0.4'
diff --git a/docs/package.json b/docs/package.json
index ff98071fc06..cee704f70d1 100644
--- a/docs/package.json
+++ b/docs/package.json
@@ -1,8 +1,8 @@
{
"scripts": {
- "dev": "vite dev",
- "build": "vite build",
- "preview": "vite build && vite preview",
+ "dev": "vike dev",
+ "build": "vike build",
+ "preview": "vike build && vike preview",
"typecheck": "tsc --noEmit --watch"
},
"dependencies": {
diff --git a/docs/pages/NODE_ENV/+Page.mdx b/docs/pages/NODE_ENV/+Page.mdx
index 340c0e5183a..0e7f3bf9187 100644
--- a/docs/pages/NODE_ENV/+Page.mdx
+++ b/docs/pages/NODE_ENV/+Page.mdx
@@ -14,7 +14,7 @@ In production (and staging):
- Make sure `process.env.NODE_ENV` is a value different than `[undefined, 'development', 'dev', '']`.
> Note that:
> - Upon starting your server in production, make sure to set `process.env.NODE_ENV`. (E.g. `$ NODE_ENV='production' node server/index.js`.)
- > - Upon building (`$ vite build`), Vite automatically sets `process.env.NODE_ENV` to `'production'`.
+ > - Upon building (`$ vike build`), Vite automatically sets `process.env.NODE_ENV` to `'production'`.
> - Upon manually triggering pre-rendering (`$ vike prerender`), Vike automatically sets `process.env.NODE_ENV` to `'production'`.
- If you use a server, make sure you don't add Vite's server middleware: it isn't needed in production and would unnecessarily bloat your production server.
diff --git a/docs/pages/add/+Page.mdx b/docs/pages/add/+Page.mdx
index 279db952f38..695b3605253 100644
--- a/docs/pages/add/+Page.mdx
+++ b/docs/pages/add/+Page.mdx
@@ -21,13 +21,28 @@ On a high-level, this is how you add Vike to your existing Vite app:
- Example: prerender.disableAutoRun
instead.
diff --git a/docs/pages/docker/+Page.mdx b/docs/pages/docker/+Page.mdx
index 013f872f9b8..ad360d02015 100644
--- a/docs/pages/docker/+Page.mdx
+++ b/docs/pages/docker/+Page.mdx
@@ -37,10 +37,10 @@ Check whether your Docker container has enough memory, and you may also need to
// package.json
{
"scripts": {
- "build": "vite build" // [!code --]
+ "build": "vike build" // [!code --]
"// Increase Node.js memory size to 3GB": "", // [!code ++]
"build": "NODE_OPTIONS=--max-old-space-size=3072 npm run build:vite", // [!code ++]
- "build:vite": "vite build" // [!code ++]
+ "build:vite": "vike build" // [!code ++]
}
}
```
diff --git a/docs/pages/hapi/+Page.mdx b/docs/pages/hapi/+Page.mdx
index 7cea70a576d..8b1101cae25 100644
--- a/docs/pages/hapi/+Page.mdx
+++ b/docs/pages/hapi/+Page.mdx
@@ -6,7 +6,7 @@ import { CommunityNote } from '../../components'
We recommend the following setup.
In development, we use *two* servers:
- 1. We use Vite's development server (`$ vite`). (It automatically includes Vike).
+ 1. We use Vite's development server. (It automatically includes Vike's server middleware.)
1. We use our hapi server *without* Vite nor Vike.
This means that in development, Vite is responsible for serving the entire frontend, while our hapi server is responsible only for serving the backend.
diff --git a/docs/pages/migration/cli/+Page.mdx b/docs/pages/migration/cli/+Page.mdx
new file mode 100644
index 00000000000..5200f6d0d53
--- /dev/null
+++ b/docs/pages/migration/cli/+Page.mdx
@@ -0,0 +1,33 @@
+import { Link } from '@brillout/docpress'
+
+Using the Vite CLI is deprecated starting from `vike@0.4.213`.
+
+> You can still use it, but you'll see following warning and support for Vite's CLI will be completely removed in the next major release.
+> ```
+> 1:18:05 PM [vike][Warning] The Vite CLI is deprecated
+> ```
+
+Use the Vike CLI instead:
+
+```json5
+// package.json
+{
+ "scripts": {
+ "dev": "vite", // [!code --]
+ "dev": "vike dev", // [!code ++]
+ "build": "vite build", // [!code --]
+ "build": "vike build", // [!code ++]
+ "preview": "vite preview", // [!code --]
+ "preview": "vike preview", // [!code ++]
+ }
+}
+```
+
+Vike's CLI doesn't have any option: use the `VITE_CONFIG` environment variable instead, see .
+
+We also recommend using Vike's JavaScript API instead of [Vite's JavaScript API](https://vite.dev/guide/api-javascript), as some features in the near future will only be available when using Vike's JavaScript API.
+
+## See also
+
+-
+-
diff --git a/docs/pages/onBeforePrerenderStart/+Page.mdx b/docs/pages/onBeforePrerenderStart/+Page.mdx
index a26979678f2..6fcdd8d6c1d 100644
--- a/docs/pages/onBeforePrerenderStart/+Page.mdx
+++ b/docs/pages/onBeforePrerenderStart/+Page.mdx
@@ -41,12 +41,12 @@ async function onBeforePrerenderStart() {
> If you don't have any parameterized route,
> then you can pre-render your app without defining any `onBeforePrerenderStart()` hook.
-> The `onBeforePrerenderStart()` hooks are called when you run $ vite build
and, consequently, are never called in development.
+> The `onBeforePrerenderStart()` hooks are called when you run $ vike build
and, consequently, are never called in development.
## For bulk data fetching
-If you have a high number of pages that are to be pre-rendered, then running the command $ vite build
may become slow.
+If you have a high number of pages that are to be pre-rendered, then running the command $ vike build
may become slow.
You can make pre-rendering significantly faster by providing the `pageContext` of pages in `onBeforePrerenderStart()` hooks.
diff --git a/docs/pages/pre-rendering/+Page.mdx b/docs/pages/pre-rendering/+Page.mdx
index 39e5c270027..e6adcafb9ce 100644
--- a/docs/pages/pre-rendering/+Page.mdx
+++ b/docs/pages/pre-rendering/+Page.mdx
@@ -4,7 +4,7 @@ import PreRenderDynamicRoutes from './PreRenderDynamicRoutes.mdx'
## What is pre-rendering?
-Pre-rendering means to render the HTML of pages at build-time (when running `$ vite build`).
+Pre-rendering means to render the HTML of pages at build-time (when running `$ vike build`).
Without pre-rendering, the HTML of a page is rendered at request-time (when the user goes to that page).
@@ -47,7 +47,7 @@ export default {
List of options: .
-Your pages' HTML will be rendered when you run `$ vite build` and the generated HTML files are available at `dist/client/`.
+Your pages' HTML will be rendered when you run `$ vike build` and the generated HTML files are available at `dist/client/`.
For a page with a parameterized route (e.g. `/movie/@movieId`), you have to use the `onBeforePrerenderStart()` hook in order to provide the list of URLs that are to be pre-rendered. The `onBeforePrerenderStart()` hook can also be used to accelerate the pre-rendering process.
@@ -55,7 +55,7 @@ For a page with a parameterized route (e.g. `/movie/@movieId`), you have to use
By default, all pages are pre-rendered. To pre-render only some pages, use the partial
option>} /> with prerender: false} />.
-If you pre-render all your pages, then you can use Vite's CLI instead of a server (`$ vite dev` and `$ vite preview`). See linked examples below.
+If you pre-render all your pages, then you can use Vike's CLI instead of a server (`$ vike dev` and `$ vike preview`). See linked examples below.
You can programmatically invoke the pre-rendering process, see .
@@ -63,19 +63,19 @@ React Example:
- prerender
option to `true`)
- prerender
option to `true`)
-