2.1.3 is not compatible with node@16, but 2.1.2 is ok

[TaylorPzreal]

Two days ago, the formidable upgrade to 2.1.3, but it is not compatible with node@16, it's required greater than v18. The 2.1.2 is ok.

with 2.1.3 and nodejs@16.14.0

ERR TypeError: os.machine is not a function
at Object.<anonymous> (node_modules/.pnpm/formidable@2.1.3/node_modules/formidable/src/Formidable.js:26:91)

[geekypandey]

I have the same issue, I was curious why this wasn't caught in the test suite?

[valera33]

I have the same problem, but my nodejs is older (v14.19.0)
2.1.2 is ok

[bonjonbovi87]

Same with the upgrade to 3.5.3 that came Friday, breaks Node 16, works on Node 18.12.0
Need to downgrade to 3.5.2

[tunnckoCore]

@bonjonbovi87 @valera33 @geekypandey @TaylorPzreal

oops, sorry folks. Will fix in a bit.

But better, please, just upgrade to non dead version, always a good thing. The v14 and 16 are dead for long time, v18 is coming to End of Life by the end of this month.

And yeah, didn't caught that because we don't test on old/non-LTS/not-even versions.

Publishing a patch version that break things is a good thing and heads up. I'm seeing downloads but people never care to upgrade, while they MUST because vulnerabilities and many more things.

v4 is coming around the corner, with matching options, speed, and a lot more; and it would require at least v18-20, so please upgrade.

[bonjonbovi87]

@bonjonbovi87 @valera33 @geekypandey @TaylorPzreal

oops, sorry folks. Will fix in a bit.

But better, please, just upgrade to non dead version, always a good thing. The v14 and 16 are dead for long time, v18 is coming to End of Life by the end of this month.

And yeah, didn't caught that because we don't test on old/non-LTS/not-even versions.

Publishing a patch version that break things is a good thing and heads up. I'm seeing downloads but people never care to upgrade, while they MUST because vulnerabilities and many more things.

v4 is coming around the corner, with matching options, speed, and a lot more; and it would require at least v18-20, so please upgrade.

Its a good kick in the ass for a pending update. There's a variety of corporate reasons to not update internal node versions (os versions, etc.). This version broke various versions of Superagent which uses this package, but there are other precautions that can be in place to prevent such a thing.

I posted more in terms of an immediate fix for end users rather than a blame, because I understand why this update would have happened.

[geekypandey]

@bonjonbovi87 @valera33 @geekypandey @TaylorPzreal

oops, sorry folks. Will fix in a bit.

But better, please, just upgrade to non dead version, always a good thing. The v14 and 16 are dead for long time, v18 is coming to End of Life by the end of this month.

And yeah, didn't caught that because we don't test on old/non-LTS/not-even versions.

Publishing a patch version that break things is a good thing and heads up. I'm seeing downloads but people never care to upgrade, while they MUST because vulnerabilities and many more things.

v4 is coming around the corner, with matching options, speed, and a lot more; and it would require at least v18-20, so please upgrade.

yes 💯 agree on upgrading the node version but since
I am working on an old project which is in maintenance phase, so upgrading won't be possible. sigh

[tunnckoCore]

@bonjonbovi87 ouch, yeah 😆

@geekypandey

Patch is coming tonight, i'll drop the os.machine thingy and it should work. Tho, os.machine seems to be existing in >=16.18, so..

But anyway, it's not a big deal, it was for even more randomness on the host machine.

[tunnckoCore]

published 2.1.4 and 3.5.4 and added a message for the 3.5.3. All should be running fine.

let me know if it still breaks.

[valera33]

published 2.1.4 and 3.5.4 and added a message for the 3.5.3. All should be running fine.

let me know if it still breaks.

works for me, thx!