Freeze policy - Make your private registry read-only to prevent changes

Freeze policy - Make your private registry read-only to prevent changes

Jun 23, 2021

Guide on how to use Bytesafe Freeze policy to control the open source software versions to what's available in an npm registry. Want to get consistent results when using npm install? Use Freeze and lock available dependencies to the ones you selected and approved.

Consistent results, regardless of who runs the installation of dependencies, when in time and regardless of the environment or system.

Make sure build systems use the exact same versions for the build, that you developed the application with. Avoid surprises with different environments getting different set of dependencies when using npm install or npm ci. Avoid wasting time on miss-matching dependency versions.

✅ 00:00 - Use Freeze policy to lock package dependencies in Bytesafe registries

✅ 00:12 - Use Freeze to get consistent results for development, test & builds

✅ 0:36 - Browse package versions from linked upstream registries directly from Bytesafe. View what versions are available to be fetched into your private registries.

✅ 1:07 - Enable Freeze from the Plugins tab. Make registry read-only and make sure other users and systems get the exact same intended versions with npm install

✅ 1:54 - Disable the Freeze policy for a registry, to fetch new versions into a registry in a controlled manner and install new dependencies to your project.

With Freeze you can keep your configured upstreams, the linked registries that are used as package sources. When Freeze is enabled these sources are "hidden" from the scope of npm install, meaning you can install your project dependencies, without failed installations.

Add the dependencies you require for your project, then Freeze the registry. Lock versions to what is available at that point in time. Giving you complete control over the package dependencies that are used for your application.

To add new package versions and keep complete control - disable the policy and add / update the versions you require. When you are finished, simply re-enable the policy.

🌐 How Bytesafe works:
🌐 More information in the Bytesafe documentation :