How to work around broken dependencies (colors.js)

[RPGillespie6]

http-server won't launch because of Marak/colors.js#285

I tried downloading older versions of http-server but the issue persists.

How do I work around this? My pipeline is broken. Please consider locking in specific known-working versioned dependencies in package.json instead of just grabbing the latest which may pull in broken/malicious/woke/protest dependencies.

[DanielRuf]

You can use resolutions or patch-package to "fix" this as described at Marak/colors.js#285 (comment).

[thornjad]

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.

[nlucero]

@thornjad Thanks for the fast response. Do we have an ETA on when will a fix be merged?

[thornjad]

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]

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.

[DanielRuf]

@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.

[thornjad]

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.