npm Blog (Archive)

The npm blog has been discontinued.

Updates from the npm team are now published on the GitHub Blog and the GitHub Changelog.

Announcing npm for Atlassian Bitbucket Pipelines and an improved Bitbucket Connect add-on

The 283,000 (!) packages in the npm Registry are only useful if it’s easy for developers to integrate them into their projects and deploy their code, so we’re excited by any chance to streamline your workflow.

If you work with Bitbucket, starting today, it’s easier than ever to install and publish npm private packages — to either your npm account or your self-hosted npm Enterprise installation.

Bitbucket Pipelines is a new continuous integration service built into Bitbucket Cloud for end-to-end visibility, from coding to deployment. We’re excited that they’re launching with npm support.

Why?

How?…

Working with private packages in the npm registry

  1. Use the bitbucket-pipelines.yml supplied in this repository.
  2. Set the NPM_TOKEN environment variable.
    • This token can be found in your local ~/.npmrc, after you log in to the registry.
  3. Enable pipelines

Working with private packages in npm Enterprise

  1. Use the bitbucket-pipelines.yml supplied in this repository.
  2. Set the NPM_TOKEN environment variable:
    • This token can be found in your local ~/.npmrc, after you log in to the registry.
  3. Set NPM_REGISTRY_URL to the full URL of your private registry (with scheme).
  4. Enable pipelines.

New in the Bitbucket Connect add-on: private packages

Alongside the new pipelines integration, the npm for Bitbucket add-on has been updated to support private modules.

This helps complete an elegant CI/CD workflow:

Get started by installing the add-on now.

Now what?

We have more exciting integrations and improvements in the … pipeline (sorry), but it helps to know what matters to you. Don’t be shy to share feedback in the comments or hit us up on Twitter.