Managed registry
You can host private software packages directly inside your Lovable workspace. Any project in your workspace can then install your team's private code without exposing it to the public.
Workspace owners and admins on an Enterprise plan who want to share private code libraries across their workspace.
Do this, in order
- 1
Go to Workspace settings, select Build & deploy, and open Managed registry.
This is where you activate and manage your private package storage.
- 2
Click Provision registry.
This instructs Lovable to create your workspace's private registry.
- 3
Enter a key name, click Create key, and immediately save the downloaded key file.
You need this secret file to authorize publishing, and it cannot be retrieved after you close the screen.
- 4
In your code project root, add the registry details to the .npmrc file and add the downloaded key as npm-key.json.
Your code project requires these files to identify the private registry and supply credentials.
- 5
Run the authentication command using the service account key.
This authorizes your code project to upload packages into your Lovable registry.
- 6
In your Lovable project chat, request the package by its full name to install it.
Lovable automatically finds and installs the package from your workspace's managed registry.
Paste this into your project
Install @my-org/ui-components and use it to replace the current button component.
Words decoded
- npm registry
- A storage hub where reusable software building blocks are published and downloaded.
- service account key
- A secret digital pass that lets computers log in and upload files without a human password.
- .npmrc
- A small configuration file that tells your setup where to download and publish packages.
- scoped package
- A package name prefixed with an organization tag, like @my-org/components, to keep it organized.
Where people get stuck
- Failing to save the service account key immediately, which permanently prevents you from accessing that key again.
- Setting up a managed registry when your packages already live on external hosts like GitHub Packages or npmjs (use build secrets instead).
- Trying to configure the registry as an editor or without an Enterprise plan.
- Leaving out the organization prefix when asking Lovable to install a scoped package.
The short version, steps, decoder and prompt on this page are written automatically from Lovable's own documentation and can lag or misread it. The official page is always the authority.