[BUG report]: Cannot convert undefined or null to object. Node v12.20.0 ~ v14

[Zhengqbbb]

Discussed in #198

Node: v12.20.0

^{Originally posted by dayney November 5, 2024}
These errors were displayed when I reinstalled：

npm WARN deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm WARN deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.

> [email protected] prepare /Users/krui/git/work/purchase-weapp
> husky install

husky - Git hooks installed
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":">=v14.21.3"} (current: {"node":"14.17.3","npm":"6.14.13"})
npm WARN notsup Not compatible with your version of node/npm: [email protected]

after, I run the following command to give the prompt is

git add package*
git cz 

Cannot convert undefined or null to object

Cannot convert undefined or null to object

• I have reproduced the issue, which is consistent with my suspicion. In v1.9.4 - https://github.com/Zhengqbbb/cz-git/blob/main/CHANGELOG.md#194-2024-07-19
• Although the error for node v22 has been fixed, it introduced an incompatible error. I apologize for the inconvenience; please downgrade to v1.9.3 first.

npm i -D [email protected]

[Zhengqbbb]

@dayney First of all, thank you very much for pointing out this BUG.

1. After investigation, this bug appeared when switching from node-fetch to node-fetch-cjs, primarily to address issues with node v22 error fix: suppress node 22 deprecated error messages #179.
2. Testing has shown that node-fetch-cjs has different issues in node v12, node v14, and node v16.

---

In response to this issue, the following changes were made in #200:

1. Changed node-fetch-cjs to dynamic import to ensure that cz-git and czg can run in node >= v12.20.
2. Added minimum version requirements for node (>= v16.5) in cases where node-fetch is needed in AI mode.

---

I plan to release v1.11.0 this weekend.
I have released a next pre-release version 🌟(v1.11.0-beta.2)🌟 for testing.
Welcome to try it out! 👀 Let me know if there are still any issues. 🎉

npm i -D cz-git@next

Node v12.20.0	Node v14.17.3

[dayney]

好的，感谢 Q.Ben Zheng ***@***.***>于2024年11月5日 周二20:20写道：

…

@dayney <https://github.com/dayney> First of all, thank you very much for pointing out this BUG. 1. After investigation, this bug appeared when switching from node-fetch to node-fetch-cjs #179 <#179>, primarily to address issues with node v22 error. 2. Testing has shown that node-fetch-cjs has different issues in node v12, node v14, and node v16. ------------------------------ In response to this issue, the following changes were made in #200 <#200>: 1. Changed node-fetch-cjs to dynamic import to ensure that cz-git and czg can run in node >= v12.20. 2. Added minimum version requirements for node (>= v16.5) in cases where node-fetch is needed in AI mode. ------------------------------ I plan to release v1.11.0 this weekend. I have released a next pre-release version 🌟(*v1.11.0-beta.2*)🌟 for testing. Welcome to try it out! 👀 Let me know if there are still any issues. 🎉 npm i -D ***@***.*** — Reply to this email directly, view it on GitHub <#199 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJPYVOICA6ZDDO446VZILDZ7CZX5AVCNFSM6AAAAABRF7VQLOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJXGAZDKNJYGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Zhengqbbb]

@dayney
The latest version 🌟(v1.11.0)🌟 released and should be resolve this issue request , please have a try. 💪
👀 Let me know if there are still any issues. 🎉

[dayney]

think you, Now it works. Q.Ben Zheng ***@***.***> 于2024年11月8日周五 23:00写道：

…

@dayney <https://github.com/dayney> The latest version 🌟(v1.11.0)🌟 released and should be resolve this issue request , please have a try. 💪 👀 Let me know if there are still any issues. 🎉 — Reply to this email directly, view it on GitHub <#199 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJPYVM74LQBUDV4EGBQD4DZ7TGYLAVCNFSM6AAAAABRF7VQLOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRUHE3TIMJUGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>