Convert package to ESM

[rekmarks]

Converts this package to an ESM module. Kudos to this guide and this issue: TypeStrong/ts-node#1997

In our organization, this is only possible for this package because it is not used anywhere else, as we rely on CommonJS extensively.

Changes in detail:

• Update package.json for ESM compatibility
• Replace all require() with import statements
• Add .js file extension to all file imports in TypeScript source files
• Update TypeScript, ESLint, and Jest configs for ESM compatibility and recommended best practices
  • TypeScript (tsconfig.json)
    • Update the module/moduleResolution fields to Node16.
    • I chose Node16 over NodeNext, as the behavior of NodeNext may change in the future. See here for details.
  • ESLint (.eslintrc.cjs)
    • parseOptions.sourceType = 'module'
  • Jest (jest.config.cjs)
    • Update the moduleNameMapper to strip the .js from local file imports. See here for details.
• Replace ts-node with tsx, which has better ESM compatibility.
  • Specifically, the former does not work with Node v20 at the moment: ERR_UNKNOWN_FILE_EXTENSION on Node v20.0.0 TypeStrong/ts-node#1997
• Update jest-it-up
  • This is so that we can use its --config option (thank you @PeterYinusa! feat(config): add -c, --config option rbardini/jest-it-up#12) to target our new .cjs config file.

[socket-security]

New, updated, and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
tsx	4.6.2	eval, network, filesystem, shell, environment	+1	525 kB	hirokiosame
jest-it-up	2.2.0...3.0.0	None	+13/-7	4.33 MB	rbardini

🚮 Removed packages: [email protected]

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: @inquirer/[email protected], [email protected], [email protected], [email protected]

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore [email protected] bar@* or ignore all packages with @SocketSecurity ignore-all

[rekmarks]

@SocketSecurity ignore @inquirer/[email protected] [email protected] [email protected] [email protected]

I've checked all of these, the authors seem legit.
@inquirer/type is not unpublished, contrary to what the Socket Security report says.

[rekmarks]

@SocketSecurity ignore [email protected]

[mcmire]

@rekmarks Sorry for the conflicts. We just merged a PR that had a wide array of changes. I want to get this PR in the next release though, so I'm happy to work on resolving these conflicts for you — just let me know.

[rekmarks]

@mcmire no, no: someone had to suffer here, and under the circumstances it should be me. I'll resolve the conflicts!

[rekmarks]

Alright, this is ready for re-review!

[mcmire]

Looks good!