Used absolute URLs

Author: jamesopstad

src/content/docs/workers/vite-plugin/debugging.mdx

@@ -8,7 +8,7 @@ description: Debugging with the Vite plugin
 ---
 
 The Cloudflare Vite plugin has debugging enabled by default and listens on port `9229`.
-You may choose a custom port or disable debugging by setting the `inspectorPort` option in the [plugin config](../api#interface-pluginconfig).
+You may choose a custom port or disable debugging by setting the `inspectorPort` option in the [plugin config](/workers/vite-plugin/api#interface-pluginconfig).
 There are two recommended methods for debugging your Workers during local development:
 
 ### DevTools

src/content/docs/workers/vite-plugin/index.mdx

@@ -30,6 +30,6 @@ Your Worker code runs inside [workerd](https://github.com/cloudflare/workerd), m
 
 {/* Add link to React Router framework guide */}To create a new application from a ready-to-go template, refer to the [React](/workers/frameworks/framework-guides/react/) or [Vue](/workers/frameworks/framework-guides/vue/) framework guides.
 
-To create a standalone Worker from scratch, refer to [Get started](./get-started/).
+To create a standalone Worker from scratch, refer to [Get started](/workers/vite-plugin/get-started/).
 
-For a more in-depth look at adapting an existing Vite project and an introduction to key concepts, refer to the [Tutorial](./tutorial/).
+For a more in-depth look at adapting an existing Vite project and an introduction to key concepts, refer to the [Tutorial](/workers/vite-plugin/tutorial/).

src/content/docs/workers/vite-plugin/migrating-from-wrangler-dev.mdx

@@ -7,7 +7,7 @@ sidebar:
 description: Migrating from wrangler dev to the Vite plugin
 ---
 
-In most cases, migrating from `wrangler dev` is straightforward and you can follow the instructions in [Get started](../get-started/).
+In most cases, migrating from `wrangler dev` is straightforward and you can follow the instructions in [Get started](/workers/vite-plugin/get-started/).
 There are a few key differences to highlight:
 
 ### Input and output Worker config files
@@ -21,14 +21,14 @@ Once you have run `vite build`, running `wrangler deploy` will automatically loc
 
 With the Cloudflare Vite plugin, Cloudflare environments are applied at dev and build time.
 Running `wrangler deploy --env some-env` is therefore not applicable and the environment to deploy should instead be set by running `CLOUDFLARE_ENV=some-env vite build`.
-See [Cloudflare Environments](../cloudflare-environments/) for more information.
+See [Cloudflare Environments](/workers/vite-plugin/cloudflare-environments/) for more information.
 
 ### Redundant fields in the Wrangler config file
 
 There are various options in the Worker config file that are ignored when using Vite, as they are either no longer applicable or are replaced by Vite equivalents.
 If these options are provided, then warnings will be printed to the console with suggestions for how to proceed.
 Examples where the Vite configuration should be used instead include `alias` and `define`.
-See [Vite Environments](../vite-environments/) for more information about configuring your Worker environments in Vite.
+See [Vite Environments](/workers/vite-plugin/vite-environments/) for more information about configuring your Worker environments in Vite.
 
 ### Local only data during local development
 

src/content/docs/workers/vite-plugin/secrets.mdx

@@ -10,7 +10,7 @@ description: Using secrets with the Vite plugin
 import { PackageManagers, WranglerConfig } from "~/components";
 
 Secrets can be provided to your Worker in local development using a [`.dev.vars`](/workers/configuration/secrets/#local-development-with-secrets) file.
-If you are using [Cloudflare Environments](../cloudflare-environments) then the relevant `.dev.vars` file will be selected.
+If you are using [Cloudflare Environments](/workers/vite-plugin/cloudflare-environments/) then the relevant `.dev.vars` file will be selected.
 For example, `CLOUDFLARE_ENV=staging vite dev` will load `.dev.vars.staging` if it exists and fall back to `.dev.vars`.
 
 :::note

src/content/docs/workers/vite-plugin/vite-environments.mdx

@@ -56,7 +56,7 @@ export default defineConfig({
 
 For more information about Vite's configuration options, see [Configuring Vite](https://vite.dev/config/).
 
-The default behavior of using the Worker name as the environment name is appropriate when you have a standalone Worker, such as an API that is accessed from your front-end application, or an [auxiliary Worker](../api/#interface-pluginconfig) that is accessed via service bindings.
+The default behavior of using the Worker name as the environment name is appropriate when you have a standalone Worker, such as an API that is accessed from your front-end application, or an [auxiliary Worker](/workers/vite-plugin/api/#interface-pluginconfig) that is accessed via service bindings.
 
 ### React Router v7