New Feature to Node.js Performance Platform: Module Repository

By Yijun

In this blog, you learn about the Module Repository feature of Node.js Performance Platform, which is developed on top of cnpm. You also will learn how you can publish a private package using Module Repository.

Preface

Module Repository

Compared with the private warehouses many enterprises build by using the open-source version of cnpm, the Module Repository has the following advantages:

  • Lower operations cost for enterprises: Traditionally, an enterprise needs to maintain at least one physical machine (ECS instance) and all the corresponding storage space if it builds a private warehouse that can meet its development scale, which can be a very costly undertaking. Module Repository eliminates the need to maintain this infrastructure.
  • A wider range of application scenarios: Private warehouses built by enterprises internally cannot allow them to share some private modules with their external partners. Module Respository, on the other hand, allows for such actions.
  • More accurate access control: Private warehouses built on top of cnpm do not allow for download/publish permission controls. However, Module Repository allows for fine-granularity authorization control over permissions, including controlling permissions by user.

In addition to covering all features of private cnpm warehouses, Module Repository in Node.js Performance Platform also supports the separation of multiple users and fine-grained access controls to meet several different enterprise development scenarios.

Currently, Module Repository is available free of charge, allowing you to take advantage of all of these advanced features.

Trial

To do it, follow the steps given here:

Create a Registry

Log on to the Registry

Use the npm/cnpm command shown in the figure to direct the npm/cnpm client warehouse to this private module warehouse, and then perform the logon operation. The account information required for the npm/cnpm client login command can be found in My Information:

Create a Scope

After the Scope is created, publish a private module with the corresponding package name into this Scope. For example, a Scope named @cloud is created in this example. You can run the npm publish command to publish the package named @cloud/quickstart to this Scope.

More Features

Original Source

Follow me to keep abreast with the latest technology news, industry insights, and developer trends.