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

Use md5 hashes instead of md4, which are no longer supported in Node.js v17.x #17

Merged
merged 2 commits into from Jan 5, 2022

Conversation

isaacs
Copy link
Contributor

@isaacs isaacs commented Nov 10, 2021

No description provided.

isaacs added a commit to tapjs/treport that referenced this pull request Nov 12, 2021
This required a lot more work than I typically like to do in a single
commit.  However, there really was no way to get it all working without
getting it ALL working, so here we are.

React is upgraded to v17, because the only way to silence all
ink-derived security advisories was to upgrade ink, which has a
dependency on a version of react-reconciler than started requiring react
17 in a minor.

This also means that there's entirely new rules about what is allowed to
go in what, the <Color> tag is gone, the <Static> tag has a whole
different interface, and some other changes.  At least Vadim had the
decency to do all this in a SemVer major, which is how it should be
done.

Silencing the ReDOS errors coming from string-length and friends
required upgrading to the newer version of string-length, which is of
course all-in on ESM now, so that stuff has been moved from being a
proper dependency to being a bundled de-ESM-ified version of those deps.
I do not like that, but until we stop supporting pre-ESM versions of
Node (and rewrite tap in ESM, which... yeah, probably not any time
soon?) there's no other way forward that I could see.

Making import-jsx work on node 17 required pulling in my git fork for
the time being, until vadimdemedes/import-jsx#17
lands in the published version.

I think it's probably time to re-think this entire approach, get away
from React and JSX in favor of something a bit less cutting-edge.
@sandro-pasquali
Copy link

@vadimdemedes Using this in a cli app so adding the necessary --openssl-legacy-provider flag is "seamless" within the hashbang directive, but for others it might be a real pain. If you need a maintainer I can volunteer.

@vadimdemedes
Copy link
Owner

Thanks @isaacs!

@sandro-pasquali Thanks for the offer, but this package is pretty much on auto pilot ;)

@vadimdemedes vadimdemedes changed the title fix: node 17 no longer supports md4 hashes, use md5 Use md4 hashes instead of md5, which are no longer supported in Node.js v17.x Jan 5, 2022
@vadimdemedes vadimdemedes changed the title Use md4 hashes instead of md5, which are no longer supported in Node.js v17.x Use md5 hashes instead of md4, which are no longer supported in Node.js v17.x Jan 5, 2022
@vadimdemedes vadimdemedes merged commit c8bc6c5 into vadimdemedes:master Jan 5, 2022
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 this pull request may close these issues.

None yet

3 participants