Closed glensc closed 1 year ago
Hi @glensc, thanks for reporting the issue. Can you please provide a reference lockfile so I can reproduce the issue?
Ok, I was able to reproduce locally. Indeed the update to use new URL()
and parse the host from it isn't strictly needed for the validate-host
option which uses hosts, and not URLs, hence this noisyness debug level isn't relevant to print an error about.
I'm pushing a fix for it.
Fixed in https://github.com/lirantal/lockfile-lint/releases/tag/lockfile-lint@4.9.3 i suppose?
Fix added in 4.9.1 but you should indeed just get the latest. Let me know if there are still any lingering issues.
Expected Behavior
Current Behavior
Updated from "lockfile-lint": "^3.0.1" to "lockfile-lint": "^4.8.0"
And getting errors like:
the
failed parsing a URL
is printed like 1000 times. I guess for every item inyarn.lock
file.Possible Solution
Roll back to
3.0.1
version.Steps to Reproduce (for bugs)
yarn add lockfile-lint@4.8.0
export 'DEBUG=*'
lockfile-lint --validate-https '--allowed-hosts=npm.example.net' '--path=yarn.lock'
Context
Your Environment