npm install fails when package-lock.json resolves to internal Artifactory URLs (ENOTFOUND / Exit handler never called)

[FaitAccompli]

Summary:

• Running npm install on a fresh clone fails because dependency tarball URLs in package-lock.json resolve to an internal Artifactory host that is not reachable for external contributors.
• This is a public repository, so contributors outside that network cannot install dependencies without regenerating the lockfile.

Environment

• OS: Linux (WSL2)
• Node: v24.12.0
• npm: 11.6.2

How to reproduce

1. Fresh clone of the repo.
2. Ensure no local corporate npm proxy config is available.
3. Run npm install.
4. Observe fetch failures to artifactory.fme.lan and install abort.

Workaround

rm -rf node_modules

Regenerate lockfile and install using public npm registry:

rm -f package-lock.json
npm i --registry=https://registry.npmjs.org/

Impact

• Blocks building and installing the extension locally