Skip to content

Conversation

@MasterOdin
Copy link
Contributor

Closes #164

PR updates jest to the latest version. I setup the CI to install an old version of jest for node < 14 so that we can keep testing them. Since the test suite is pretty simple, and largely unchanging, I don't think this will pose much of a problem going forward, but if it does, easy to drop testing for node < 14.


- name: Update npm
if: matrix.node-version == '6.x'
run: npm install -g npm@^5
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should have been removed in #165, but missed it, whoops!

@eriktrom
Copy link
Member

eriktrom commented Mar 12, 2025

I will merge this and ship this after were done with the *Promise refactor, aka, once we implement getSocket with promise or callback - so that work is chunked in the commit line for easier understanding (by us years from now or someone else looking to learn the library)

@eriktrom
Copy link
Member

I setup the CI to install an old version of jest for node < 14

oh sweet - I literally pondered about this and you thought the same thing - thank you


- name: Install jest for node < 14
if: matrix.node-version == '10.x' || matrix.node-version == '12.x'
run: npm install jest@^27.5.1
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perfecto

Glad to have you around, I went through this all manually on my machine(s) as well but you're on top of it! very nice

@eriktrom
Copy link
Member

so this had a conflict b/c we actually shipped 1.0.34 without mkdirp removed - rebase against mater again and it'll merge cleanly now

Signed-off-by: Matthew Peveler <[email protected]>
@MasterOdin
Copy link
Contributor Author

MasterOdin commented Mar 14, 2025

@eriktrom Rebased.

so this had a conflict b/c we actually shipped 1.0.34 without mkdirp removed - rebase against mater again and it'll merge cleanly now

My bad on not updating package-lock.json. Though, 1.0.34 did ship with mkdirp removed for consumers of this library (as it wasn't in the package.json file), it just still was installed for direct users of this repo.

@eriktrom
Copy link
Member

Though, 1.0.34 did ship with mkdirp removed for consumers of this library (as it wasn't in the package.json file), it just still was installed for direct users of this repo

I wondered this same thing so I made a little app last night to and it would track the lockfile package.json - worth noting for knowledge sake

and no worries, all good, not the end of the world, I should have caught it anyway

@eriktrom eriktrom merged commit 7c622b6 into http-party:master Mar 14, 2025
19 checks passed
@MasterOdin MasterOdin deleted the chore-jest branch July 30, 2025 19:32
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.

upgrade Jest from 24.9.0 to 29.7.0

2 participants