How to work around broken dependencies (colors.js) #781
Comments
|
You can use resolutions or patch-package to "fix" this as described at Marak/colors.js#285 (comment). |
|
Ah crap, not this again. At least this time colors isn't as integral to http-server as when ecstatic did this. Give me a little time to catch up this latest drama and I'll accept one of the two PRs for this. |
|
@thornjad Thanks for the fast response. Do we have an ETA on when will a fix be merged? |
|
Barring any hiccups, I'll merge and release a fix today. I'll also try to backport the fix to the v13 line because I know there are some unrelated issues with the v14 release for some folks. |
thornjad
changed the title
|
Merged #785, just going to see what the tests do (I know Node 17 has some problems) before tagging a release. I'll backport to v13 later today. |
|
@thornjad Node 17 and and other Node release with an odd major version number is not recommended in general as these are no LTS releases but short living test branches. |
|
That's why I haven't put it on a high priority, but I'd prefer to support it. They are more than just test branches, while not LTS, it is a proper full release, and provide a view of what the next LTS will contain. But its especially frustrating that it works fine in every local environment I've put it in, but gh-actions fails consistently. |
|
🎉 Published to npm! Check for versions v14.1.0 or v13.1.0 |
|
I see the 14.1.0 Github release, but npm doesn't seem to have it yet :( |
|
npm has a lot of caching in place to deal with the enormity of the traffic it serves, so it might take a while, maybe even a few hours, to show up for everyone. I've verified it did publish though, so its just a matter of time! |
|
I see it now. Thanks. I figured npm was behind with caching. After an hour I got a little worried. |
http-serverwon't launch because of Marak/colors.js#285I tried downloading older versions of
http-serverbut the issue persists.How do I work around this? My pipeline is broken. Please consider locking in specific known-working versioned dependencies in
package.jsoninstead of just grabbing the latest which may pull in broken/malicious/woke/protest dependencies.The text was updated successfully, but these errors were encountered: