From 439a73f3222987896f556b64628bdbcb5d9454c3 Mon Sep 17 00:00:00 2001 From: HaeJun Seo Date: Tue, 21 Feb 2023 17:26:13 +0900 Subject: [PATCH] docs: update rollup docs links (#12130) --- docs/guide/api-plugin.md | 2 +- docs/guide/migration.md | 2 +- packages/vite/CHANGELOG.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/guide/api-plugin.md b/docs/guide/api-plugin.md index 79b2279fa5eed0..7102b047df9480 100644 --- a/docs/guide/api-plugin.md +++ b/docs/guide/api-plugin.md @@ -479,7 +479,7 @@ A fair number of Rollup plugins will work directly as a Vite plugin (e.g. `@roll In general, as long as a Rollup plugin fits the following criteria then it should just work as a Vite plugin: -- It doesn't use the [`moduleParsed`](https://rollupjs.org/guide/en/#moduleparsed) hook. +- It doesn't use the [`moduleParsed`](https://rollupjs.org/plugin-development/#moduleparsed) hook. - It doesn't have strong coupling between bundle-phase hooks and output-phase hooks. If a Rollup plugin only makes sense for the build phase, then it can be specified under `build.rollupOptions.plugins` instead. It will work the same as a Vite plugin with `enforce: 'post'` and `apply: 'build'`. diff --git a/docs/guide/migration.md b/docs/guide/migration.md index ec355c9890218b..cf6352c73ab0a5 100644 --- a/docs/guide/migration.md +++ b/docs/guide/migration.md @@ -4,7 +4,7 @@ Vite is now using [Rollup 3](https://github.com/vitejs/vite/issues/9870), which allowed us to simplify Vite's internal asset handling and has many improvements. See the [Rollup 3 release notes here](https://github.com/rollup/rollup/releases/tag/v3.0.0). -Rollup 3 is mostly compatible with Rollup 2. If you are using custom [`rollupOptions`](../config/build-options.md#rollup-options) in your project and encounter issues, refer to the [Rollup migration guide](https://rollupjs.org/guide/en/#migration) to upgrade your config. +Rollup 3 is mostly compatible with Rollup 2. If you are using custom [`rollupOptions`](../config/build-options.md#rollup-options) in your project and encounter issues, refer to the [Rollup migration guide](https://rollupjs.org/migration/) to upgrade your config. ## Modern Browser Baseline change diff --git a/packages/vite/CHANGELOG.md b/packages/vite/CHANGELOG.md index 01b8c71e5dea83..7d666053ddd22a 100644 --- a/packages/vite/CHANGELOG.md +++ b/packages/vite/CHANGELOG.md @@ -648,7 +648,7 @@ See [3.2.0-beta.0 changelog](https://github.com/vitejs/vite/blob/v3.2.0-beta.4/p } } ``` - Read the updated [Rollup Plugin docs](https://rollupjs.org/guide/en/#build-hooks) for more information. + Read the updated [Rollup Plugin docs](https://rollupjs.org/plugin-development/#build-hooks) for more information. > **Note** > After Vite 3.1, you are no longer going to see `[vite] hot updated` log messages in the browser console. These messages have been moved to the debug channel ([#8855](https://github.com/vitejs/vite/issues/8855)). Check your browser docs to [show debug logs](https://developer.chrome.com/docs/devtools/console/log/#level).