Skip to content

[BUG] Using --install-strategy = "linked" ignores the strict-ssl config #8340

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
2 tasks done
Treycos opened this issue Jun 2, 2025 · 0 comments
Open
2 tasks done
Labels
Bug thing that needs fixing Needs Triage needs review for next steps

Comments

@Treycos
Copy link

Treycos commented Jun 2, 2025

Is there an existing issue for this?

  • I have searched the existing issues

This issue exists in the latest npm version

  • I am using the latest npm

Current Behavior

Running npm i with the following configuration:

Global configuration since we're running behind a restrictive firewall:

npm config set strict-ssl false

Config file in our project .npmrc:

install-strategy = "linked"

The command output gives us a c:

npm error: Error: self-signed certificate in certificate chain
///
npm error:  code: 'SELF_SIGNED_CERT_IN_CHAIN'

Running the install script using the default strategy works fine (no cert error)

Expected Behavior

The strict-ssl config param should work the same way no matter which install-strategy is selected

Steps To Reproduce

  1. Install packages with self-signed cetificates
  2. Set strict-ssl to false
  3. Set install-strategy to linked
  4. Run npm install
  5. Get error SELF_SIGNED_CERT_IN_CHAIN

Environment

  • npm: 11.4.1
  • Node.js: 20.18.1
  • OS Name: Windows 11
  • npm config:
cafile = // File path
prefix = // Appdata path
registry = // Company registry
strict-ssl = false
unsafe-perm = true
@Treycos Treycos added Bug thing that needs fixing Needs Triage needs review for next steps labels Jun 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug thing that needs fixing Needs Triage needs review for next steps
Projects
None yet
Development

No branches or pull requests

1 participant