Use markdown syntax in mdx where possible

Closes #788

Author: lukekarrys

.eslintrc.js

@@ -43,8 +43,6 @@ module.exports = {
  },
  rules: {
  'no-irregular-whitespace': 'off',
- 'jsx-a11y/anchor-has-content': 'off',
- 'react/jsx-no-target-blank': 'off',
  },
  },
  ],

cli/lib/extract.js

@@ -37,6 +37,12 @@ const unpackTarball = async ({release, cwd, dir}) => {
  // the v6 version of the funding page has json not inside a code
  .replace(/(:\n\n)(\s{4}"funding": {)/g, '$1```json\n$2')
  .replace(/^(\s{4}]$)(\n\n)/gm, '$1\n```$2')
+ // anchor links to markdown. this regex does need to match spaces and newlines since the source markdown
+ // already has some links where attributes are separated by newlines
+ .replace(
+ /<a[\s\n]href="(.*?)"(?:[\s\n]target="_blank")?(?:[\s\n]rel="[a-z\s]+")?>(.*?)<\/a>/g,
+ (_, href, text) => `[${href}](${text.trim()})`,
+ )
  )
  }
 

content/cli/v10/commands/npm-audit.mdx

@@ -99,13 +99,13 @@ The `sig` is generated using the following template: `${package.name}@${package.
 
 Keys response:
 
-- `expires`: null or a simplified extended <a href="https://en.wikipedia.org/wiki/ISO_8601" target="_blank">ISO 8601 format</a>: `YYYY-MM-DDTHH:mm:ss.sssZ`
+- `expires`: null or a simplified extended [https://en.wikipedia.org/wiki/ISO_8601](ISO 8601 format): `YYYY-MM-DDTHH:mm:ss.sssZ`
 - `keydid`: sha256 fingerprint of the public key
 - `keytype`: only `ecdsa-sha2-nistp256` is currently supported by the npm CLI
 - `scheme`: only `ecdsa-sha2-nistp256` is currently supported by the npm CLI
 - `key`: base64 encoded public key
 
-See this <a href="https://registry.npmjs.org/-/npm/v1/keys" target="_blank">example key's response from the public npm registry</a>.
+See this [https://registry.npmjs.org/-/npm/v1/keys](example key's response from the public npm registry).
 
 ### Audit Endpoints
 

content/cli/v10/commands/npm-team.mdx

@@ -55,7 +55,7 @@ Teams must always be fully qualified with the organization/scope they belong to
 
 If you have two-factor authentication enabled in `auth-and-writes` mode, then you can provide a code from your authenticator with `[--otp <otpcode>]`. If you don't include this then you will be taken through a second factor flow based on your `authtype`.
 
-- create / destroy: Create a new team, or destroy an existing one. Note: You cannot remove the `developers` team, <a href="https://docs.npmjs.com/about-developers-team" target="_blank">learn more.</a>
+- create / destroy: Create a new team, or destroy an existing one. Note: You cannot remove the `developers` team, [https://docs.npmjs.com/about-developers-team](learn more.)
 
  Here's how to create a new team `newteam` under the `org` org:
 

content/cli/v10/commands/npm-unpublish.mdx

@@ -41,9 +41,7 @@ redirect_from:
 npm unpublish [<package-spec>]
 ```
 
-To learn more about how the npm registry treats unpublish, see our <a
-href="https://docs.npmjs.com/policies/unpublish" target="_blank"
-rel="noopener noreferrer"> unpublish policies</a>
+To learn more about how the npm registry treats unpublish, see our [https://docs.npmjs.com/policies/unpublish](unpublish policies)
 
 ### Warning
 

content/cli/v6/commands/npm-team.mdx

@@ -41,7 +41,7 @@ Teams must always be fully qualified with the organization/scope they belong to
 
 If you have two-factor authentication enabled in `auth-and-writes` mode, then you can provide a code from your authenticator with `[--otp <otpcode>]`. If you don't include this then you will be prompted.
 
-- create / destroy: Create a new team, or destroy an existing one. Note: You cannot remove the `developers` team, <a href="https://docs.npmjs.com/about-developers-team" target="_blank">learn more.</a>
+- create / destroy: Create a new team, or destroy an existing one. Note: You cannot remove the `developers` team, [https://docs.npmjs.com/about-developers-team](learn more.)
 - add / rm: Add a user to an existing team, or remove a user from a team they belong to.
 
 - ls: If performed on an organization name, will return a list of existing teams under that organization. If performed on a team, it will instead return a list of all users belonging to that particular team.

content/cli/v6/commands/npm-unpublish.mdx

@@ -45,7 +45,7 @@ If no version is specified, or if all versions are removed then the root package
 
 Even if a package version is unpublished, that specific name and version combination can never be reused. In order to publish the package again, a new version number must be used. If you unpublish the entire package, you may not publish any new versions of that package until 24 hours have passed.
 
-To learn more about how unpublish is treated on the npm registry, see our <a href="https://www.npmjs.com/policies/unpublish" target="_blank" rel="noopener noreferrer"> unpublish policies</a>.
+To learn more about how unpublish is treated on the npm registry, see our [https://www.npmjs.com/policies/unpublish](unpublish policies).
 
 ### See Also
 

content/cli/v7/commands/npm-team.mdx

@@ -41,7 +41,7 @@ Teams must always be fully qualified with the organization/scope they belong to
 
 If you have two-factor authentication enabled in `auth-and-writes` mode, then you can provide a code from your authenticator with `[--otp <otpcode>]`. If you don't include this then you will be prompted.
 
-- create / destroy: Create a new team, or destroy an existing one. Note: You cannot remove the `developers` team, <a href="https://docs.npmjs.com/about-developers-team" target="_blank">learn more.</a>
+- create / destroy: Create a new team, or destroy an existing one. Note: You cannot remove the `developers` team, [https://docs.npmjs.com/about-developers-team](learn more.)
 
  Here's how to create a new team `newteam` under the `org` org:
 

content/cli/v7/commands/npm-unpublish.mdx

@@ -21,9 +21,7 @@ redirect_from:
 
 ### Synopsis
 
-To learn more about how the npm registry treats unpublish, see our <a
-href="https://docs.npmjs.com/policies/unpublish" target="_blank"
-rel="noopener noreferrer"> unpublish policies</a>
+To learn more about how the npm registry treats unpublish, see our [https://docs.npmjs.com/policies/unpublish](unpublish policies)
 
 #### Unpublishing a single version of a package
 

content/cli/v8/commands/npm-audit.mdx

@@ -79,13 +79,13 @@ The `sig` is generated using the following template: `${package.name}@${package.
 
 Keys response:
 
-- `expires`: null or a simplified extended <a href="https://en.wikipedia.org/wiki/ISO_8601" target="_blank">ISO 8601 format</a>: `YYYY-MM-DDTHH:mm:ss.sssZ`
+- `expires`: null or a simplified extended [https://en.wikipedia.org/wiki/ISO_8601](ISO 8601 format): `YYYY-MM-DDTHH:mm:ss.sssZ`
 - `keydid`: sha256 fingerprint of the public key
 - `keytype`: only `ecdsa-sha2-nistp256` is currently supported by the npm CLI
 - `scheme`: only `ecdsa-sha2-nistp256` is currently supported by the npm CLI
 - `key`: base64 encoded public key
 
-See this <a href="https://registry.npmjs.org/-/npm/v1/keys" target="_blank">example key's response from the public npm registry</a>.
+See this [https://registry.npmjs.org/-/npm/v1/keys](example key's response from the public npm registry).
 
 ### Audit Endpoints