fix!: Make publicDir and modulesDir relative to project root (#1216)

Author: aklinker1

docs/guide/essentials/assets.md

@@ -29,7 +29,7 @@ img.src = imageUrl;
 
 ## `/public` Directory
 
-Files inside `<srcDir>/public/` are copied into the output folder as-is, without being processed by WXT's bundler.
+Files inside `<rootDir>/public/` are copied into the output folder as-is, without being processed by WXT's bundler.
 
 Here's how you access them:
 
@@ -54,6 +54,10 @@ img.src = imageUrl;
 
 :::
 
+:::warning
+Assets in the `public/` directory are **_not_** accessible in content scripts by default. To use a public asset in a content script, you must add it to your manifest's [`web_accessible_resources` array](/api/reference/wxt/type-aliases/UserManifest#web-accessible-resources).
+:::
+
 ## Inside Content Scripts
 
 Assets inside content scripts are a little different. By default, when you import an asset, it returns just the path to the asset. This is because Vite assumes you're loading assets from the same hostname.

docs/guide/essentials/project-structure.md

@@ -61,14 +61,14 @@ After enabling it, your project structure should look like this:
 📂 {rootDir}/
 📁 .output/
 📁 .wxt/
+📁 modules/
+📁 public/
 📂 src/
    📁 assets/
    📁 components/
    📁 composables/
    📁 entrypoints/
    📁 hooks/
-   📁 modules/
-   📁 public/
    📁 utils/
    📄 app.config.ts
 📄 .env

packages/i18n/README.md

@@ -49,7 +49,7 @@ However, it does have one major downside:
    helloWorld: Hello world!
    ```
 
-   > `@wxt-dev/i18n` supports the standard messages format, so if you already have localization files at `<srcDir>/public/_locale/<lang>/messages.json`, you don't need to convert them to YAML or refactor them - just move them to `<srcDir>/locales/<lang>.json` and they'll just work out of the box!
+   > `@wxt-dev/i18n` supports the standard messages format, so if you already have localization files at `<rootDir>/public/_locale/<lang>/messages.json`, you don't need to convert them to YAML or refactor them - just move them to `<srcDir>/locales/<lang>.json` and they'll just work out of the box!
 
 4. To get a translation, use the auto-imported `i18n` object or import it manually:
 

packages/wxt-demo/src/modules/auto-icons.ts renamed to packages/wxt-demo/modules/auto-icons.ts

@@ -88,14 +88,14 @@ export async function resolveConfig(
     srcDir,
     mergedConfig.entrypointsDir ?? 'entrypoints',
   );
-  const modulesDir = path.resolve(srcDir, mergedConfig.modulesDir ?? 'modules');
   if (await isDirMissing(entrypointsDir)) {
     logMissingDir(logger, 'Entrypoints', entrypointsDir);
   }
+  const modulesDir = path.resolve(root, mergedConfig.modulesDir ?? 'modules');
   const filterEntrypoints = mergedConfig.filterEntrypoints?.length
     ? new Set(mergedConfig.filterEntrypoints)
     : undefined;
-  const publicDir = path.resolve(srcDir, mergedConfig.publicDir ?? 'public');
+  const publicDir = path.resolve(root, mergedConfig.publicDir ?? 'public');
   const typesDir = path.resolve(wxtDir, 'types');
   const outBaseDir = path.resolve(root, mergedConfig.outDir ?? '.output');
   const modeSuffixes: Record<string, string | undefined> = {

packages/wxt-demo/src/modules/example.ts renamed to packages/wxt-demo/modules/example.ts

@@ -38,7 +38,7 @@ export interface InlineConfig {
    */
   entrypointsDir?: string;
   /**
-   * @default "${config.srcDir}/modules"
+   * @default "${config.root}/modules"
    */
   modulesDir?: string;
   /**