Skip to content
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

@blueprintjs/eslint-config@6.0.10 causing EUNSUPPORTEDPROTOCOL #7289

Closed
ihsw opened this issue Mar 1, 2025 · 1 comment · Fixed by #7305
Closed

@blueprintjs/eslint-config@6.0.10 causing EUNSUPPORTEDPROTOCOL #7289

ihsw opened this issue Mar 1, 2025 · 1 comment · Fixed by #7305

Comments

@ihsw
Copy link

ihsw commented Mar 1, 2025

Environment

  • @blueprintjs/eslint-config@6.0.10
  • macOS 15.3.1

Code Sandbox

n/a

Steps to reproduce

  1. npm install @blueprintjs/eslint-config@6.0.10

Actual behavior

ihsw@Mac eslint-config % npm install @blueprintjs/eslint-config@6.0.10
npm error code EUNSUPPORTEDPROTOCOL
npm error Unsupported URL Type "patch:": patch:eslint-plugin-header@npm%3A3.1.1#~/.yarn/patches/eslint-plugin-header-npm-3.1.1-402265ec6f.patch
npm error A complete log of this run can be found in: /Users/ihsw/.npm/_logs/2025-03-01T14_28_33_771Z-debug-0.log

Expected behavior

ihsw@Mac eslint-config % npm install @blueprintjs/eslint-config@6.0.10

up to date, audited 328 packages in 761ms

128 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

Possible solution

Don't use patch: deps?

https://github.com/palantir/blueprint/blob/develop/packages/eslint-config/package.json#L10

Downgrading to "@blueprintjs/eslint-config": "6.0.9" worked for me.

EDIT: it seems someone has published a 6.1.11 version just now, this is interesting.

@ggdouglas
Copy link
Contributor

Hey @ihsw , thanks for the report!

This dependency was patched as part of upgrading to ESLint 9: #7252 / #7252 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants