#NPM CONFIG SET RESET INSTALL#
#NPM CONFIG SET RESET DOWNLOAD#

How do you check this? Of course, you can first just re-run the npm config listcommand and check that the configuration line has gone. Now, all npm operations referring to scoped packages will use the default registry.

remove the configuration entry associating the scope with the old (retired) SAP-specific registry. So let’s do this together now: npm config delete will do exactly what we want, i.e. It’s this association that needs to be removed (so that npm will use the default NPM registry for any scoped packages). The second one is the current (and now unwanted) scope/registry association for SAP packages, there as a result of me running the npm config set command at some stage in the past. The first one is for my own scoped packages which are on GitHub (see the GitHub packages feature for more information on this). settings that I have made) which have been stored in an. The semicolon prefixed lines are comments, and the chunk of configuration in the middle is my user specific configuration (i.e. 'npm config ls -l' to show all defaults. Here’s an example from my machine right now: ▶ npm config list

You can examine your NPM configuration with npm config. Not only that, but it’s no longer recommended either, as updates to SAP packages will only be made available on the default NPM registry and the SAP-specific registry will eventually disappear (see the Updates section). So we’d set configuration for npm to tell it to use a specific registry for packages, like this: npm config set with the recent migration of SAP packages to the main, default NPM registry at, while the scoping of the packages remain, the configuration setting associating the scope to the SAP-specific registry ( ) is no longer required.

#NPM CONFIG SET RESET INSTALL#

Here’s an example (note that this is how it’s worked up until now, for illustration purposes): npm install there’s no specific association between the scope and the SAP NPM registry where the package was available, npmwould assume and use the default registry at.

#NPM CONFIG SET RESET DOWNLOAD#

On your system, NPM will exist mainly as the command npm, and when you ask it to install a package for you it will download the package from the registry associated with the specified scope. This is the basis of what SAP did three years ago with the launching of the SAP NPM registry – see the post from Sven Kohlhaas back in 2017. For example, the package in the scope.Ĭombine this scope idea with the fact that there can be more than one registry (that’s why is called the “default” registry) and it means that it’s possible to, for example, have packages belonging to a certain scope published to and available at a different registry. The scope starts with an sign and is joined to the package name with a slash. įor organisational purposes, a package can belong to a scope (think of it as similar to a namespace). Node.js packages (also referred to as NPM packages) can be made available publicly in registries.

The default package manager for Node.js is the Node Package Manager (NPM). So now is the time to remove any NPM configuration you may have set to point to the SAP-specific registry for SAP packages.ĭo it like this: npm config delete you’re on Windows, you may need to put the part in double quotes). Moreover, updates to SAP packages will in future only be available from the default public registry, and the SAP-specific registry will be phased out. Over the past few weeks the team has been busy migrating these packages to the default public registry. Since 2017 SAP has made Node.js packages available at an SAP-specific registry. 🚨See the Updates section for an important announcement. This post tells you what you need to know – and do – about the recent migration of SAP Node.js packages to the default registry at.

Npm config set reset