Skip to main content

Publish shared packages

Publish

(dnb-web-shared-libs and dnb-web-shared-tools)​

The packages in these repositories will be published to the Nexus npm registry. Once publish is done, the new package versions will be visible in https://nexus.tech.dnb.no/nexus/#browse/browse:dcf-npm. They can then be installed as a dependency to other packages.

Package requirements​

The only requirement for a package to be published from these repositories is to have a valid package.json file with publishConfig set to:

package.json
"publishConfig": {
    "registry": "https://nexus.tech.dnb.no/nexus/repository/dcf-npm/",
    "access": "restricted"
},

This is automatically set when you created the package using the template generator.

When is a package published?​

Here are the three main events when implementing a new future or fix and how they trigger a publish:

EventWhat is published
MR is created/updated including changesetPackage snapshot is published
MR is mergedNone
New package is releasedPackage for the version is published

When is a package released?​

Packages are versioned using changeset. They are released once the release MR (called Version packages) MR is merged to main branch:

Release MR!