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
If you are using a private artifactory, you can set the env variable `NPM_CONFIG_REGISTRY` for the worker to the url of your artifactory. If the private registry is exposing custom certificates,`DENO_CERT` and `DENO_TLS_CA_STORE` env variables can be used as well (see [Deno documentaion](https://docs.deno.com/runtime/manual/getting_started/setup_your_environment#environment-variables) for more info on those options).
46
+

47
+
48
+
On EE, go to `Instance settings -> Core -> NPM Config Registry`.
49
+
50
+
Set the registry URL: `https://npm.pkg.github.com/OWNER` (replace `OWNER` with your GitHub username or organization name).
51
+
52
+
#### Private NPM packages requiring token
53
+
54
+
:::caution
55
+
56
+
Currently, deno does not support private npm packages requiring tokens (but support private npm registries). Bun however does.
57
+
58
+
:::
59
+
60
+
If a token is required, append `:_authToken=<your url>` to the URL.
61
+
62
+
Combining the two, you can import private packages from npm
If the private registry is exposing custom certificates,`DENO_CERT` and `DENO_TLS_CA_STORE` env variables can be used as well (see [Deno documentaion](https://docs.deno.com/runtime/manual/getting_started/setup_your_environment#environment-variables) for more info on those options).
0 commit comments