You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 13, 2021. It is now read-only.
Copy file name to clipboardExpand all lines: exercises/01/readme.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,11 +12,11 @@ After completing these steps you'll have a working local environment for develop
12
12
13
13
The CDS command line tool is the heart of everything you do when developing CAP services locally. It is Node.js based and comes in the form of an NPM package (which further depends on other packages). The package and its dependencies are in the `@sap` namespace and are available from the [SAP NPM registry](https://blogs.sap.com/2017/05/16/sap-npm-registry-launched-making-the-lives-of-node.js-developers-easier/).
14
14
15
-
:point_right: First, relate the `@sap` namespace to the SAP NPM registry:
15
+
:point_right: First, delete the reation of the `@sap` namespace to the SAP NPM registry (It's not updated anymore since June 2020):
16
16
17
17
```sh
18
18
user@host:~
19
-
=> npm set@sap:registry=https://npm.sap.com
19
+
=> npm config delete "@sap:registry"
20
20
```
21
21
22
22
:point_right: Check that this setting is now saved in your configuration, with:
0 commit comments