CLI documentation update from CI

Author: npm-cli-bot

cli-cache.json

@@ -2,5 +2,5 @@
   "v8": "aa8fff11cdab94fff1a2160ee5241f5f4632e96b",
   "v9": "64763a341e7aa5b456e696f956759bf9b3440dc1",
   "v10": "f69c403700acb05dbb56d8516bca5130627e597c",
-  "v11": "d006583e20731e8ae55cee94c3b7bd23cbd6f2d0"
+  "v11": "5d82d0b4a4bd1424031fb68b4df740c1bbe5b172"
 }

content/cli/v11/configuring-npm/package-json.mdx

@@ -305,12 +305,6 @@ These can not be included.
 
 The "exports" provides a modern alternative to "main" allowing multiple entry points to be defined, conditional entry resolution support between environments, and preventing any other entry points besides those defined in "exports". This encapsulation allows module authors to clearly define the public interface for their package. For more details see the [node.js documentation on package entry points](https://nodejs.org/api/packages.html#package-entry-points)
 
-### type
-
-The `type` field defines the module format that Node.js should use for `.js` files in the package.
-
-For more details, see the [Node.js documentation](https://nodejs.org/api/packages.html#type).
-
 ### main
 
 The main field is a module ID that is the primary entry point to your program. That is, if your package is named `foo`, and a user installs it, and then does `require("foo")`, then your main module's exports object will be returned.