v2.0.1

What's Changed

• Fixes for private packages and registries by @miguel-silva in #20
• Fixes for packages whose versions are objects rather than strings.

New Contributors

• @miguel-silva made their first contribution in #20

Full Changelog: v2.0.0...v2.0.1

v2.0.0

Breaking Changes

• Remove npmRegistry option. Document registryFetchOptions. (#16)

Previously there were two ways to pass in the npm registry to use: npmRegistry and registryFetchOptions.registry. The npmRegistry option didn't work and there's no reason to have two ways to do this, so we removed npmRegistry and documented registryFetchOptions.registry instead.

To migrate:

{
-  npmRegistry: "https://private-registry.com/"
+  registryFetchOptions: {
+    registry: "https://private-registry.com/"
+  }
}

Fixes

• Add missing typedefs (#15 @mstergianis)

Maintenance

• Add CI/CD (#17)

v1.3.0

Features

• Support for registryFetchOptions config. Allows passing username, password, and/or token to npm registry. (#12 #11)

v1.2.0

Features

• New --usePackageJSON option (#10 via @jsmapr1) Documentation

v1.1.0

Features

• Support for npmRegistry config option. This lets you set which npm registry to download packages from (#8 via @prof-schnitzel)

v1.0.4

Fixes

• Support for scoped npm packages (#9 via @prof-schnitzel )

v1.0.3

Fixes

• Fixed windows compatibility (#7 via @prof-schnitzel )
• Fix CLI usage (#2 via @jsmapr1 )

Maintenance

• Fix typo in readme (#3 via @jsmapr1)

v1.0.2

Fixes

• Reduce tarball size e9bcb4e

v1.0.1

Fixes

• Fix type definitions 1027cba

v1.0.0

Initial release

• See readme for documentation