-
-
Notifications
You must be signed in to change notification settings - Fork 17.3k
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
Solve issues for Node.js CITGM #5489
Comments
Yes, I fixed that a long time ago, also in this repo too, which is probably why you cannot reproduce it while running tests locally from clone? |
Great point @dougwilson. Now I am thinking that maybe is because CITGM is using
|
Oh, interesting. I guess that is true, if citgm uses published vereion it wouldn't be there. I was confused bc I saw the log saying downloading from github.com. I guess we can queue up a parch release quickly to make it available to citgm, without going through the minor release timeline. |
Yeah, a patch release sounds great 👍 |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Curent status We are just waiting for this PR to be merged, the CI is passing 🥳 |
Hi team! I was researching a bit about the current issues with CITGM, there is a PR nodejs/citgm#977 open to re-add express, but one of the tests is failling.
How to reproduce?
nvm use 20.11.0
npm i -g citgm
citgm express
What is the error?
I was not able to reproduce this error while running the tests locally from a express clone, but after doing a bit of research seems like it is related to expressjs/body-parser@368a93a ?
As a side note, I will update the CI to include the most recent Node.js versions:
The text was updated successfully, but these errors were encountered: