From f5857e263ccf5648ce7d4260c5868e3e940a7258 Mon Sep 17 00:00:00 2001 From: John O'Sullivan Date: Wed, 24 Apr 2019 18:57:05 -0400 Subject: [PATCH] Clarify usage of bundledDependencies I spent a couple hours debugging the fact that package names in that key aren't supposed to include their versions! Assumed that it would need to have the same syntax as when running `npm install`. Thought this would be a good contribution for future readers. --- doc/files/package.json.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/doc/files/package.json.md b/doc/files/package.json.md index 95e77d34c5f9f..6324caf64a517 100644 --- a/doc/files/package.json.md +++ b/doc/files/package.json.md @@ -648,7 +648,8 @@ If we define a package.json like this: we can obtain `awesome-web-framework-1.0.0.tgz` file by running `npm pack`. This file contains the dependencies `renderized` and `super-streams` which can be installed in a new project by executing `npm install -awesome-web-framework-1.0.0.tgz`. +awesome-web-framework-1.0.0.tgz`. Note that the package names do not include +any versions, as that information is specified in `dependencies`. If this is spelled `"bundleDependencies"`, then that is also honored.