npm run format

shmam · shmam · commit 26b353d85ccd · 2025-12-03T10:53:34.000-05:00
diff --git a/content/cli/v10/commands/npm-publish.mdx b/content/cli/v10/commands/npm-publish.mdx
@@ -32,6 +32,7 @@ Publishes a package to the registry so that it can be installed by name.
 <Note>
 
 **Important:** Publishing to npm requires either:
+
 - Two-factor authentication (2FA) enabled on your account, OR
 - A granular access token with bypass 2FA enabled (for CI/CD workflows)
 
diff --git a/content/cli/v11/commands/npm-publish.mdx b/content/cli/v11/commands/npm-publish.mdx
@@ -52,6 +52,7 @@ Publish the package in the current directory:
 <Note>
 
 **Important:** Publishing to npm requires either:
+
 - Two-factor authentication (2FA) enabled on your account, OR
 - A granular access token with bypass 2FA enabled (for CI/CD workflows)
 
diff --git a/content/cli/v6/commands/npm-publish.mdx b/content/cli/v6/commands/npm-publish.mdx
@@ -35,6 +35,7 @@ Publishes a package to the registry so that it can be installed by name. All fil
 <Note>
 
 **Important:** Publishing to npm requires either:
+
 - Two-factor authentication (2FA) enabled on your account, OR
 - A granular access token with bypass 2FA enabled (for CI/CD workflows)
 
diff --git a/content/cli/v7/commands/npm-publish.mdx b/content/cli/v7/commands/npm-publish.mdx
@@ -35,6 +35,7 @@ Publishes a package to the registry so that it can be installed by name.
 <Note>
 
 **Important:** Publishing to npm requires either:
+
 - Two-factor authentication (2FA) enabled on your account, OR
 - A granular access token with bypass 2FA enabled (for CI/CD workflows)
 
diff --git a/content/cli/v8/commands/npm-publish.mdx b/content/cli/v8/commands/npm-publish.mdx
@@ -32,6 +32,7 @@ Publishes a package to the registry so that it can be installed by name.
 <Note>
 
 **Important:** Publishing to npm requires either:
+
 - Two-factor authentication (2FA) enabled on your account, OR
 - A granular access token with bypass 2FA enabled (for CI/CD workflows)
 
diff --git a/content/cli/v9/commands/npm-publish.mdx b/content/cli/v9/commands/npm-publish.mdx
@@ -32,6 +32,7 @@ Publishes a package to the registry so that it can be installed by name.
 <Note>
 
 **Important:** Publishing to npm requires either:
+
 - Two-factor authentication (2FA) enabled on your account, OR
 - A granular access token with bypass 2FA enabled (for CI/CD workflows)
 
diff --git a/content/getting-started/setting-up-your-npm-user-account/about-two-factor-authentication.mdx b/content/getting-started/setting-up-your-npm-user-account/about-two-factor-authentication.mdx
@@ -23,6 +23,7 @@ When you enable 2FA, you will be prompted for a second form of authentication be
 <Note variant="warning">
 
 **Important:** Publishing packages to npm now requires either:
+
 - Two-factor authentication (2FA) enabled on your account, OR
 - A [granular access token with bypass 2FA enabled][granular-tokens] (for CI/CD workflows)
 
diff --git a/content/getting-started/setting-up-your-npm-user-account/configuring-two-factor-authentication.mdx b/content/getting-started/setting-up-your-npm-user-account/configuring-two-factor-authentication.mdx
@@ -9,6 +9,7 @@ You can enable two-factor authentication (2FA) on your npm user account to prote
 <Note variant="warning">
 
 **Important:** Publishing packages to npm now requires either:
+
 - Two-factor authentication (2FA) enabled on your account, OR
 - A [granular access token with bypass 2FA enabled][creating-token] (for CI/CD workflows)
 
diff --git a/content/packages-and-modules/contributing-packages-to-the-registry/creating-and-publishing-private-packages.mdx b/content/packages-and-modules/contributing-packages-to-the-registry/creating-and-publishing-private-packages.mdx
@@ -84,6 +84,7 @@ By default, scoped packages are published with private visibility.
 <Note>
 
 **Important:** Before you can publish, you must have either:
+
 - [Two-factor authentication (2FA)][config-2fa] enabled on your account, OR
 - A [granular access token with bypass 2FA enabled][creating-token] (required for CI/CD workflows)
 
diff --git a/content/packages-and-modules/contributing-packages-to-the-registry/creating-and-publishing-scoped-public-packages.mdx b/content/packages-and-modules/contributing-packages-to-the-registry/creating-and-publishing-scoped-public-packages.mdx
@@ -80,6 +80,7 @@ By default, scoped packages are published with private visibility. To publish a
 <Note>
 
 **Important:** Before you can publish, you must have either:
+
 - [Two-factor authentication (2FA)][config-2fa] enabled on your account, OR
 - A [granular access token with bypass 2FA enabled][creating-token] (required for CI/CD workflows)
 
diff --git a/content/packages-and-modules/contributing-packages-to-the-registry/creating-and-publishing-unscoped-public-packages.mdx b/content/packages-and-modules/contributing-packages-to-the-registry/creating-and-publishing-unscoped-public-packages.mdx
@@ -61,6 +61,7 @@ npm install path/to/my-package
 <Note>
 
 **Important:** Before you can publish, you must have either:
+
 - [Two-factor authentication (2FA)][config-2fa] enabled on your account, OR
 - A [granular access token with bypass 2FA enabled][creating-token] (required for CI/CD workflows)
 
diff --git a/content/packages-and-modules/contributing-packages-to-the-registry/creating-node-js-modules.mdx b/content/packages-and-modules/contributing-packages-to-the-registry/creating-node-js-modules.mdx
@@ -38,11 +38,10 @@ exports.printMsg = function() {
 1. Publish your package to npm:
 
    <Note>
-   
+
    **Important:** Before you can publish, you must have either [two-factor authentication (2FA)][config-2fa] enabled on your account, or a [granular access token with bypass 2FA enabled][creating-token] for CI/CD workflows.
-   
-   </Note>
 
+   </Note>
    - For [private packages][priv-pkg-pub] and [unscoped packages][unscoped-pkg-pub], use `npm publish`.
    - For [scoped public packages][scoped-pkg-pub], use `npm publish --access public`
 
diff --git a/content/packages-and-modules/securing-your-code/requiring-2fa-for-package-publishing-and-settings-modification.mdx b/content/packages-and-modules/securing-your-code/requiring-2fa-for-package-publishing-and-settings-modification.mdx
@@ -36,11 +36,10 @@ For CI/CD workflows, consider using [trusted publishing](/trusted-publishers), w
 4. Under "Publishing access", select the requirements to publish a package.
 
    <Note>
-   
+
    **Note:** All packages now require either two-factor authentication or a granular access token with bypass 2FA enabled to publish. This is the default setting for all new packages.
-   
-   </Note>
 
+   </Note>
    1. **Require two-factor authentication or granular access tokens** (Default)  
       With this option, maintainers must have two-factor authentication enabled for their account. If they publish a package interactively, using the `npm publish` command, they will be required to enter 2FA credentials when they perform the publish. However, maintainers may also create a [granular access token with bypass 2FA enabled][creating-granular-access-token] and use that to publish. A second factor is _not_ required when using these specific token types, making them useful for continuous integration and continuous deployment workflows.
 
