From 223588812351a3470f786174edeb27cd90bfbb37 Mon Sep 17 00:00:00 2001 From: Christian Duerr Date: Mon, 3 Mar 2025 20:04:32 +0100 Subject: [PATCH] Update expected NPM firewall error --- docs/artifact_repositories/npm.md | 24 +++++++----------------- 1 file changed, 7 insertions(+), 17 deletions(-) diff --git a/docs/artifact_repositories/npm.md b/docs/artifact_repositories/npm.md index f932a580..09a592a5 100644 --- a/docs/artifact_repositories/npm.md +++ b/docs/artifact_repositories/npm.md @@ -37,25 +37,15 @@ npm config set registry https://%2F:@n > > Do not accidentally save your token into your shell history. -A blocked package will show up in `npm` output as missing: +A blocked package will show up in `npm` output as E403: ```text -npm error code E404 -npm error 404 Not Found - GET http://:***@npm.phylum.io/ -npm error 404 -npm error 404 '@*' is not in this registry. -npm error 404 -npm error 404 Note that you can also install from a -npm error 404 tarball, folder, http url, or git url. -``` - -Alternatively, if only a specific version is affected: - -```text -npm error code ETARGET -npm error notarget No matching version found for @. -npm error notarget In most cases you or one of your dependencies are requesting -npm error notarget a package version that doesn't exist. +npm error code E403 +npm error 403 Could not download @ due to policy violations: +npm error 403 Blocked by package firewall. +npm error 403 In most cases, you or one of your dependencies are requesting +npm error 403 a package version that is forbidden by your security policy, or +npm error 403 on a server you do not have access to. ``` If you're using `pnpm`, the output will look like this: