3.3.3

Updated dependencies to latest versions

3.3.2

Updated dependencies to latest versions

3.3.1

Updated dependencies to latest versions

3.3.0

• --binaryAbi, --binaryArch, --binaryPlatform arguments are now optional. Default values are used from the current Node.js process running registry-sync.
• local packages (i.e. those referenced by a file: url in the lock file) are now omitted from synchronization
• updated dependencies to latest versions

Thanks to @RolKau for the new features!

3.2.5

Updated dependencies to latest versions

3.2.4

Updated dependencies to latest versions

3.2.3

• Fix #39 (aliases like "npm:[email protected]" as version values in package-lock.json)

3.2.2

• added an optional --registryToken option for defining a Bearer token for the registry
• updated dependencies to latest versions

Thanks to @csjablonkay for the new feature!

3.2.1

Updated dependencies to latest versions

3.2.0

• added support for yarn.lock files (so, --manifest can be pointed to one)
• added --dryRun option for printing packages that would be downloaded (but do not download them)
• added a configuration example to README.md for a simple docker-based registry server
• reverted functionality in 3.1.0: "some packages (sqlite3, for example) are incorrectly missing binaries for an N-API version although they claim to have them. package.json files are updated with the available N-API version set for those packages to avoid download errors when npm install tries to access them in the local repository later." The problem is specific to sqlite3 v5.0.1 and will be hopefully fixed by the project soon.

Thanks to @juhahe for the new features!