fix register command.

[SkidGod4444]

Date: 08-10-2024

Developer Name: Saidev Dhal

---

• Closes Fix register command & update jest version #266

Description

Fixed the npm run register command. So that it will not cause any error next time.

Documentation Updated?

• Yes
• No

Under Feature Flag

• Yes
• No

Database Changes

• Yes
• No

Breaking Changes

• Yes
• No

Development Tested?

• Yes
• No

Screenshots

Screenshot 1

Test Coverage

Screenshot 1

Additional Notes

This issue as existing before i just wanted to fix it so updated the package command.

[vinit717]

Can you add an issue ticket for this
describing the error

[SkidGod4444]

Can you add an issue ticket for this describing the error

Done, sir added the issue ticket.

[iamitprakash]

I want to know, how it was working before

[joyguptaa]

I want to know, how it was working before

Hello @iamitprakash I am also not sure about how it was working before. We faced this issue while trying to set up the Discord-slash-command on Saidev's system.
Also when I was doing my setup in February for the discord-slash command, I, too, faced this issue. And to this day, it doesn't work on my system.

[SkidGod4444]

I want to know how it was working before

Earlier versions of Node.js were more forgiving with module resolution, allowing ts-node-esm to work. With Node.js v20, stricter rules were introduced, causing issues like ERR_UNKNOWN_FILE_EXTENSION. These new rules require better handling of ESM-specific features, which is why ts-node-esm is failing now while ts-node (which uses CommonJS) continues to work fine.

Hence, systems having Node.js v20 or earlier are facing this issue, and others are not.

Reference: GitHub issue.

[iamitprakash]

I want to know, how it was working before

Earlier versions of Node.js were more forgiving with module resolution, allowing ts-node-esm to work. With Node.js v20, stricter rules were introduced, causing issues like ERR_UNKNOWN_FILE_EXTENSION. These new rules require better handling of ESM-specific features, which is why ts-node-esm might fail now while ts-node (which uses CommonJS) continues to work fine.

Hence systems having Node.js v20 or earlier are facing this issue and others are not.

Reference: GitHub issue.

Hello @SkidGod4444 I will not go with your might word, need crystal clear answers

[SkidGod4444]

I want to know, how it was working before

Earlier versions of Node.js were more forgiving with module resolution, allowing ts-node-esm to work. With Node.js v20, stricter rules were introduced, causing issues like ERR_UNKNOWN_FILE_EXTENSION. These new rules require better handling of ESM-specific features, which is why ts-node-esm might fail now while ts-node (which uses CommonJS) continues to work fine.
Hence systems having Node.js v20 or earlier are facing this issue and others are not.
Reference: GitHub issue.

Hello @SkidGod4444 I will not go with your might word, need crystal clear answers

Sorry for that MIGHT word but that is the appropriate reason for this issue. I also updated the comment now:

#264 (comment)