Set Up a Local Compile (Managed Package)

For the managed package runtime, to set up a local compile, add credentials and a compiler version if needed.

1. To set up the local compile, request a Username and Password for the private NPM repository. If you have previously used OmniOut, use the same credentials.
   If you don’t have credentials, request an NPM repository access key from your customer representative by filing a support case with the subject: Request for Access Key to Vlocity's Private NPM Repository at https://repo.vlocity.com/repository/vlocity-public/ for using OmniOut / IDX CLI.
2. To add the credentials to the .npmrc file in the user's home directory, run this command:

   npm config set @omnistudio:registry https://repo.vlocity.com/repository/vlocity-public/
   npm config set _auth <In Nexus - Use the following for a base64 representation of "user:password"> 

   The file looks like this:

   @omnistudio:registry=https://repo.vlocity.com/repository/vlocity-public/
   //repo.vlocity.com/repository/vlocity-public/:username=USERNAME
   //repo.vlocity.com/repository/vlocity-public/:_password="PASSWORD"
   

   The other namespaces for the compiler are @vlocity-ins and @vlocity-cme.

   If set up correctly, this command should work:

   npm install @omnistudio/omniscript-lwc-compiler
   

   You can also add this line to your job file:

   npmAuthKey: KEY
   lwcCompilerVersion: '900.469'
   

   If you don’t set lwcCompilerVersion, the latest compiler version is used. To force the compiler version, use the package version in Salesforce (for example, 900.469).