isolate-package - npm Package Compare versions

Comparing version 1.20.0-0 to 1.20.0-1

package.json

 {
   "name": "isolate-package",
-  "version": "1.20.0-0",
+  "version": "1.20.0-1",
   "description": "Isolate a monorepo package with its shared dependencies to form a self-contained directory, compatible with Firebase deploy",
@@ -5,0 +5,0 @@ "author": "Thijs Koerselman",

README.md

@@ -188,2 +188,20 @@ # Isolate Package
 
+### forceNpm
+
+Type: `boolean`, default: `false`
+
+By default the isolate process will generate output based on the package manager
+that you are using for your monorepo, but your deployment target might not be
+compatible with that package manager.
+
+It should not really matter what package manager is used in de deployment as
+long as the versions match your original lockfile.
+
+By setting this option to `true` you are forcing the isolate output to use NPM.
+A package-lock file will be generated based on the contents of node_modules and
+therefore should match the versions in your original lockfile.
+
+This way you can enjoy using PNPM or Yarn for your monorepo, while your
+deployment requires NPM.
+
 ### buildDirName
@@ -190,0 +208,0 @@

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

263048

increased by0.65%

Lines of code

2379

increased by0.76%

Number of lines in readme file

376

increased by5.03%

No dependency changes