chore(docs): fix .json links on markdown

claudiahdz · claudiahdz · commit c17dba64ed5d · 2019-10-31T18:54:31.000+02:00
diff --git a/docs/content/cli-commands/npm-bugs.md b/docs/content/cli-commands/npm-bugs.md
@@ -47,4 +47,4 @@ The base URL of the npm package registry.
 * [npm-registry](/using-npm/registry)
 * [npm-config](/cli-commands/npm-config)
 * [npmrc](/configuring-npm/npmrc)
-* [package.json](/configuring-npm/package.json)
+* [package.json](/configuring-npm/package-json)
diff --git a/docs/content/cli-commands/npm-build.md b/docs/content/cli-commands/npm-build.md
@@ -31,4 +31,4 @@ directly, run:
 * [npm-install](/cli-commands/npm-install)
 * [npm-link](/cli-commands/npm-link)
 * [npm-scripts](/using-npm/scripts)
-* [package.json](/configuring-npm/package.json)
+* [package.json](/configuring-npm/package-json)
diff --git a/docs/content/cli-commands/npm-config.md b/docs/content/cli-commands/npm-config.md
@@ -80,6 +80,6 @@ global config.
 
 * [npm-folders](/configuring-npm/folders)
 * [npm-config](/cli-commands/npm-config)
-* [package.json](/configuring-npm/package.json)
+* [package.json](/configuring-npm/package-json)
 * [npmrc](/configuring-npm/npmrc)
 * [npm](/cli-commands/npm)
diff --git a/docs/content/cli-commands/npm-docs.md b/docs/content/cli-commands/npm-docs.md
@@ -50,4 +50,4 @@ The base URL of the npm package registry.
 * [npm-registry](/using-npm/registry)
 * [npm-config](/cli-commands/npm-config)
 * [npmrc](/configuring-npm/npmrc)
-* [package.json](/configuring-npm/package.json)
+* [package.json](/configuring-npm/package-json)
diff --git a/docs/content/cli-commands/npm-help.md b/docs/content/cli-commands/npm-help.md
@@ -40,6 +40,6 @@ Set to `"browser"` to view html help content in the default web browser.
 * [npm-folders](/configuring-npm/folders)
 * [npm-config](/cli-commands/npm-config)
 * [npmrc](/configuring-npm/npmrc)
-* [package.json](/configuring-npm/package.json)
+* [package.json](/configuring-npm/package-json)
 * [npm-help-search](/cli-commands/npm-help-search)
 * [npm-index](/cli-commands/npm-index)
diff --git a/docs/content/cli-commands/npm-init.md b/docs/content/cli-commands/npm-init.md
@@ -69,6 +69,6 @@ will create a scoped package.
 ### See Also
 
 * <https://github.com/isaacs/init-package-json>
-* [package.json](/configuring-npm/package.json)
+* [package.json](/configuring-npm/package-json)
 * [npm-version](/cli-commands/npm-version)
 * [npm-scope](/using-npm/scope)
diff --git a/docs/content/cli-commands/npm-install.md b/docs/content/cli-commands/npm-install.md
@@ -35,7 +35,7 @@ files exist. See [package-lock.json](/docs/configuring-npm/package-lock.json) an
 
 A `package` is:
 
-* a) a folder containing a program described by a [`package.json`](/docs/configuring-npm/package.json) file
+* a) a folder containing a program described by a [`package.json`](/docs/configuring-npm/package-json) file
 * b) a gzipped tarball containing (a)
 * c) a url that resolves to (b)
 * d) a `<name>@<version>` that is published on the registry (see [`npm-registry`](npm-registry)) with (c)
@@ -58,7 +58,7 @@ after packing it up into a tarball (b).
     directory) as a global package.
 
     By default, `npm install` will install all modules listed as dependencies
-    in [`package.json`](/docs/configuring-npm/package.json).
+    in [`package.json`](/docs/configuring-npm/package-json).
 
     With the `--production` flag (or when the `NODE_ENV` environment variable
     is set to `production`), npm will not install modules listed in
@@ -188,7 +188,7 @@ after packing it up into a tarball (b).
 * `npm install [<@scope>/]<name>@<version range>`:
 
     Install a version of the package matching the specified version range.  This
-    will follow the same rules for resolving dependencies described in [`package.json`](/docs/configuring-npm/package.json).
+    will follow the same rules for resolving dependencies described in [`package.json`](/docs/configuring-npm/package-json).
 
     Note that most version ranges must be put in quotes so that your shell will
     treat it as a single argument.
@@ -491,4 +491,4 @@ affects a real use-case, it will be investigated.
 * [npm-dist-tag](/cli-commands/npm-dist-tag)
 * [npm-uninstall](/cli-commands/npm-uninstall)
 * [npm-shrinkwrap](/cli-commands/npm-shrinkwrap)
-* [package.json](/configuring-npm/package.json)
+* [package.json](/configuring-npm/package-json)
diff --git a/docs/content/cli-commands/npm-link.md b/docs/content/cli-commands/npm-link.md
@@ -86,7 +86,7 @@ npm link @myorg/privatepackage
 ### See Also
 
 * [npm-developers](/using-npm/developers)
-* [package.json](/configuring-npm/package.json)
+* [package.json](/configuring-npm/package-json)
 * [npm-install](/cli-commands/npm-install)
 * [npm-folders](/configuring-npm/folders)
 * [npm-config](/cli-commands/npm-config)
diff --git a/docs/content/cli-commands/npm-publish.md b/docs/content/cli-commands/npm-publish.md
@@ -27,7 +27,7 @@ package, as well as details on how the package is built.
 
 By default npm will publish to the public registry. This can be overridden by
 specifying a different default registry or using a [`npm-scope`](npm-scope) in the name
-(see [`package.json`](/docs/configuring-npm/package.json)).
+(see [`package.json`](/docs/configuring-npm/package-json)).
 
 * `<folder>`:
   A folder containing a package.json file
diff --git a/docs/content/cli-commands/npm-shrinkwrap.md b/docs/content/cli-commands/npm-shrinkwrap.md
@@ -27,8 +27,8 @@ of package locks in npm, see [npm-package-locks](npm-package-locks).
 * [npm-install](/cli-commands/npm-install)
 * [npm-run-script](/cli-commands/npm-run-script)
 * [npm-scripts](/using-npm/scripts)
-* [package.js](/configuring-npm/package.json)
+* [package.js](/configuring-npm/package-json)
 * [npm-package-locks](/configuring-npm/package-locks)
-* [package-lock.json](/configuring-npm/package-lock.json)
-* [npm-shrinkwrap.json](/configuring-npm/shrinkwrap.json)
+* [package-lock.json](/configuring-npm/package-lock-json)
+* [npm-shrinkwrap.json](/configuring-npm/shrinkwrap-json)
 * [npm-ls](/cli-commands/npm-ls)
diff --git a/docs/content/cli-commands/npm-version.md b/docs/content/cli-commands/npm-version.md
@@ -129,6 +129,6 @@ Note that you must have a default GPG key set up in your git config for this to
 * [npm-init](/cli-commands/npm-init)
 * [npm-run-script](/cli-commands/npm-run-script)
 * [npm-scripts](/using-npm/scripts)
-* [package.json](/docs/configuring-npm/package.json)
+* [package.json](/docs/configuring-npm/package-json)
 * [semver](/using-npm/semver)
 * [config](/using-npm/config)
diff --git a/docs/content/cli-commands/npm.md b/docs/content/cli-commands/npm.md
@@ -163,7 +163,7 @@ reproduction to report.
 
 ### See Also
 * [npm-help](/cli-commands/npm-help)
-* [package.json](/configuring-npm/package.json)
+* [package.json](/configuring-npm/package-json)
 * [npm-install](/cli-commands/npm-install)
 * [npm-config](/cli-commands/npm-config)
 * [npmrc](/configuring-npm/npmrc)
diff --git a/docs/content/configuring-npm/folders.md b/docs/content/configuring-npm/folders.md
@@ -214,7 +214,7 @@ cannot be found elsewhere.  See [`package.json`](/docs/configuring-npm/package.j
 
 ### See also
 
-* [package.json](/configuring-npm/package.json)
+* [package.json](/configuring-npm/package-json)
 * [npm-install](/cli-commands/npm-install)
 * [npm-pack](/cli-commands/npm-pack)
 * [npm-cache](/cli-commands/npm-cache)
diff --git a/docs/content/configuring-npm/npmrc.md b/docs/content/configuring-npm/npmrc.md
@@ -99,5 +99,5 @@ manner.
 * [npm-folders](/configuring-npm/folders)
 * [npm-config](/cli-commands/npm-config)
 * [config](/using-npm/config)
-* [package.json](/configuring-npm/package.json)
+* [package.json](/configuring-npm/package-json)
 * [npm](/cli-commands/npm)
diff --git a/docs/content/configuring-npm/package-lock-json.md b/docs/content/configuring-npm/package-lock-json.md
@@ -28,7 +28,7 @@ various purposes:
 
 One key detail about `package-lock.json` is that it cannot be published, and it
 will be ignored if found in any place other than the toplevel package. It shares
-a format with [npm-shrinkwrap.json](shrinkwrap.json), which is essentially the same file, but
+a format with [npm-shrinkwrap.json](docs/configuring-npm/shrinkwrap-json), which is essentially the same file, but
 allows publication. This is not recommended unless deploying a CLI tool or
 otherwise using the publication process for producing production packages.
 
@@ -143,7 +143,7 @@ The dependencies of this dependency, exactly as at the top level.
 ### See also
 
 * [npm-shrinkwrap](/cli-commands/npm-shrinkwrap)
-* [npm-shrinkwrap.json](/configuring-npm/shrinkwrap.json)
+* [npm-shrinkwrap.json](/configuring-npm/shrinkwrap-json)
 * [npm-package-locks](/configuring-npm/package-locks)
-* [package.json](/configuring-npm/package.json)
+* [package.json](/configuring-npm/package-json)
 * [npm-install](/cli-commands/npm-install)
diff --git a/docs/content/configuring-npm/package-locks.md b/docs/content/configuring-npm/package-locks.md
@@ -10,7 +10,7 @@ description: An explanation of npm lockfiles
 
 ### Description
 
-Conceptually, the "input" to [`npm-install`](/docs/cli-commands/npm-install) is a [package.json](/docs/configuring-npm/package.json), while its
+Conceptually, the "input" to [`npm-install`](/docs/cli-commands/npm-install) is a [package.json](/docs/configuring-npm/package-json), while its
 "output" is a fully-formed `node_modules` tree: a representation of the
 dependencies you declared. In an ideal world, npm would work like a pure
 function: the same `package.json` should produce the exact same `node_modules`
@@ -83,7 +83,7 @@ author are not the same person, there's no way for A's author to say
 that he or she does not want to pull in newly published versions of C
 when B hasn't changed at all.
 
-To prevent this potential issue, npm uses [package-lock.json](package-lock.json) or, if present,
+To prevent this potential issue, npm uses [package-lock.json](/docs/configuring-npm/package-lock-json) or, if present,
 [npm-shrinkwrap.json](shrinkwrap.json). These files are called package locks, or lockfiles.
 
 Whenever you run `npm install`, npm generates or updates your package lock,
@@ -112,7 +112,7 @@ which will look something like this:
 This file describes an *exact*, and more importantly *reproducible*
 `node_modules` tree. Once it's present, any future installation will base its
 work off this file, instead of recalculating dependency versions off
-[package.json](/docs/configuring-npm/package.json).
+[package.json](/docs/configuring-npm/package-json).
 
 The presence of a package lock changes the installation behavior such that:
 
@@ -177,7 +177,7 @@ pre-`npm@5.7.0` versions of npm 5, albeit a bit more noisily. Note that if
 ### See Also
 
 * https://medium.com/@sdboyer/so-you-want-to-write-a-package-manager-4ae9c17d9527
-* [package.json](/configuring-npm/package.json)
-* [package-lock.json](/configuring-npm/package-lock.json)
-* [npm-shrinkwrap.json](/configuring-npm/shrinkwrap.json)
+* [package.json](/configuring-npm/package-json)
+* [package-lock.json](/configuring-npm/package-lock-json)
+* [npm-shrinkwrap.json](/configuring-npm/shrinkwrap-json)
 * [npm-shrinkwrap](/cli-commands/npm-shrinkwrap)
diff --git a/docs/content/configuring-npm/shrinkwrap-json.md b/docs/content/configuring-npm/shrinkwrap-json.md
@@ -24,11 +24,11 @@ Additionally, if both `package-lock.json` and `npm-shrinkwrap.json` are present
 in a package root, `package-lock.json` will be ignored in favor of this file.
 
 For full details and description of the `npm-shrinkwrap.json` file format, refer
-to the manual page for [package-lock.json](package-lock.json).
+to the manual page for [package-lock.json](/docs/configuring-npm/package-lock-json).
 
 ### See also
 
 * [npm-shrinkwrap](/cli-commands/npm-shrinkwrap)
-* [package-lock.json](/configuring-npm/package-lock.json)
-* [package.json](/configuring-npm/package.json)
+* [package-lock.json](/configuring-npm/package-lock-json)
+* [package.json](/configuring-npm/package-json)
 * [npm-install](/cli-commands/npm-install)
diff --git a/docs/content/using-npm/config.md b/docs/content/using-npm/config.md
@@ -134,7 +134,7 @@ then the user could change the behavior by doing:
 npm config set foo:port 80
 ```
 
-See [package.json](/docs/configuring-npm/package.json) for more information.
+See [package.json](/docs/configuring-npm/package-json) for more information.
 
 ### Config Settings
 
diff --git a/docs/content/using-npm/developers.md b/docs/content/using-npm/developers.md
@@ -58,7 +58,7 @@ an argument to `git checkout`.  The default is `master`.
 You need to have a `package.json` file in the root of your project to do
 much of anything with npm.  That is basically the whole interface.
 
-See [`package.json`](/docs/configuring-npm/package.json) for details about what goes in that file.  At the very
+See [`package.json`](/docs/configuring-npm/package-json) for details about what goes in that file.  At the very
 least, you need:
 
 * name:
@@ -245,7 +245,7 @@ Tell the world how easy it is to install your program!
 
 * [npm](/cli-commands/npm)
 * [npm-init](/cli-commands/npm-init)
-* [package.json](/configuring-npm/package.json)
+* [package.json](/configuring-npm/package-json)
 * [npm-scripts](/using-npm/scripts)
 * [npm-publish](/cli-commands/npm-publish)
 * [npm-adduser](/cli-commands/npm-adduser)
diff --git a/docs/content/using-npm/registry.md b/docs/content/using-npm/registry.md
@@ -81,7 +81,7 @@ published at all, or
 `"publishConfig":{"registry":"http://my-internal-registry.local"}`
 to force it to be published only to your internal registry.
 
-See [`package.json`](/docs/configuring-npm/package.json) for more info on what goes in the package.json file.
+See [`package.json`](/docs/configuring-npm/package-json) for more info on what goes in the package.json file.
 
 ### Will you replicate from my registry into the public one?
 
diff --git a/docs/content/using-npm/scripts.md b/docs/content/using-npm/scripts.md
@@ -265,7 +265,7 @@ above.
   only will prevent some optional features, then it's better to just
   print a warning and exit successfully.
 * Try not to use scripts to do what npm can do for you.  Read through
-  [`package.json`](/docs/configuring-npm/package.json) to see all the things that you can specify and enable
+  [`package.json`](/docs/configuring-npm/package-json) to see all the things that you can specify and enable
   by simply describing your package appropriately.  In general, this
   will lead to a more robust and consistent state.
 * Inspect the env to determine where to put things.  For instance, if
@@ -284,6 +284,6 @@ above.
 ### See Also
 
 * [npm-run-script](/cli-commands/npm-run-script)
-* [package.json](/configuring-npm/package.json)
+* [package.json](/configuring-npm/package-json)
 * [npm-developers](/using-npm/developers)
 * [npm-install](/cli-commands/npm-install)
