chore: Fix auto-fixable markdownlint errors (#1710)

2025-06-04 17:40:00 -05:00
parent 1eda21f63f
commit d9cb0ebcc8
18 changed files with 99 additions and 32 deletions
@@ -50,7 +50,9 @@ Changing execution order is simple:
     📄 0.my-module.ts
     📄 1.another-module.ts
  ```
+
 - If you need to run an NPM module after user modules, just make it a user module and prefix the filename with a number!
+
  ```ts
  // modules/2.i18n.ts
  export { default } from '@wxt-dev/i18n/module';
@@ -235,6 +235,7 @@ If you want to use the `activeTab` permission or the `browser.action.onClicked`

 1. Delete the [Popup entrypoint](/guide/essentials/entrypoints#popup) if it exists
 2. Add the `action` key to your manifest:
+
   ```ts
   export default defineConfig({
     manifest: {
@@ -76,6 +76,7 @@ To create a standalone content script that only includes a CSS file:

 1. Create the CSS file: `entrypoints/example.content.css`
 2. Use the `build:manifestGenerated` hook to add the content script to the manifest:
+
   ```ts [wxt.config.ts]
   export default defineConfig({
     hooks: {
@@ -459,6 +460,7 @@ If you don't need to run your UI in the same frame as the content script, you ca
 WXT provides a helper function, [`createIframeUi`](/api/reference/wxt/utils/content-script-ui/iframe/functions/createIframeUi), which simplifies setting up the IFrame.

 1. Create an HTML page that will be loaded into your IFrame:
+
   ```html
   <!-- entrypoints/example-iframe.html -->
   <!doctype html>
@@ -473,7 +475,9 @@ WXT provides a helper function, [`createIframeUi`](/api/reference/wxt/utils/cont
     </body>
   </html>
   ```
+
 1. Add the page to the manifest's `web_accessible_resources`:
+
   ```ts [wxt.config.ts]
   export default defineConfig({
     manifest: {
@@ -486,6 +490,7 @@ WXT provides a helper function, [`createIframeUi`](/api/reference/wxt/utils/cont
     },
   });
   ```
+
 1. Create and mount the IFrame:

   ```ts
@@ -580,7 +580,7 @@ body {
 }
 ```

-Follow Vite's guide to setup your preprocessor of choice: https://vitejs.dev/guide/features.html#css-pre-processors
+Follow Vite's guide to setup your preprocessor of choice: <https://vitejs.dev/guide/features.html#css-pre-processors>

 CSS entrypoints are always unlisted. To add CSS to a content script, see the [Content Script](/guide/essentials/content-scripts#css) docs.

@@ -9,6 +9,7 @@ This page discusses how to setup internationalization using the vanilla `browser
 ## Usage

 1. Add `default_locale` to your manifest:
+
   ```ts
   export default defineConfig({
     manifest: {
@@ -16,6 +17,7 @@ This page discusses how to setup internationalization using the vanilla `browser
     },
   });
   ```
+
 2. Create `messages.json` files in the `public/` directory:

   <!-- prettier-ignore -->
@@ -41,9 +43,11 @@ This page discusses how to setup internationalization using the vanilla `browser
   ```

 3. Get the translation:
+
   ```ts
   browser.i18n.getMessage('helloWorld');
   ```
+
 4. _Optional_: Add translations for extension name and description:

 ```json
@@ -62,6 +62,7 @@ Here are some examples:
  ```

 - HTML file only built for all targets other than `chrome`:
+
  ```html
  <!doctype html>
  <html lang="en">
@@ -105,4 +105,4 @@ To use a different framework, you will likely have to disable auto-imports, setu

 It is possible to do, but will require a bit more setup. Refer to Vitest's setup for an example of how to setup a test environment:

-https://github.com/wxt-dev/wxt/blob/main/packages/wxt/src/testing/wxt-vitest-plugin.ts
+<https://github.com/wxt-dev/wxt/blob/main/packages/wxt/src/testing/wxt-vitest-plugin.ts>
@@ -9,18 +9,23 @@ WXT provides a "module system" that let's you run code at different steps in the
 There are two ways to add a module to your project:

 1. **NPM**: install an NPM package, like [`@wxt-dev/auto-icons`](https://www.npmjs.com/package/@wxt-dev/auto-icons) and add it to your config:
+
   ```ts [wxt.config.ts]
   export default defineConfig({
     modules: ['@wxt-dev/auto-icons'],
   });
   ```
+
   > Searching for ["wxt module"](https://www.npmjs.com/search?q=wxt%20module) on NPM is a good way to find published WXT modules.
+
 2. **Local**: add a file to your project's `modules/` directory:
+
   ```
   <rootDir>/
     modules/
       my-module.ts
   ```
+
   > To learn more about writing your own modules, read the [Writing Modules](/guide/essentials/wxt-modules) docs.

 ## Module Options