feat!: esm (#811)

* feat!: esm

* test: generated nuts vs. ts-node

* chore: __filename

* test: nut fixes for esm

* chore: dep bumps

* test: none of that experimental stuff

* chore: bump deps for testkit windows hangs

Author: mshanemc

.eslintignore

@@ -0,0 +1 @@
+*.cjs/

.gitignore

@@ -47,3 +47,5 @@ oclif.manifest.json
 
 # ignore generated nut tests
 test/nuts/generated/
+
+oclif.lock

.lintstagedrc.cjs

@@ -0,0 +1,3 @@
+module.exports = {
+  '**/*.{js,json,md}?(x)': () => 'npm run reformat',
+};

.lintstagedrc.js

@@ -1,8 +1,9 @@
 {
-  "require": "ts-node/register,source-map-support/register",
+  "require": ["ts-node/register"],
   "watch-extensions": "ts",
   "watch-files": ["src", "test"],
   "recursive": true,
   "reporter": "spec",
-  "timeout": 10000
+  "timeout": 10000,
+  "node-option": ["loader=ts-node/esm"]
 }

.mocharc.json

@@ -29,7 +29,7 @@
 1.  Build and lint the code: `yarn build`
 1.  Create a branch off main for new work: `git checkout -b <branch_name>` _Suggestion: use branch_name format of initials/work-title_. For external contributors, please fork the main branch of the repo instead and PR the fork to the main branch.
 1.  Make code changes and build: `yarn build`
-1.  Run changed commands: `./bin/dev project:deploy:start --help`
+1.  Run changed commands: `./bin/dev.js project:deploy:start --help`
 1.  Write tests and run: `yarn test` (unit) and/or `yarn test:nuts` (NUTs)
 1.  Show all changed files: `git status`
 1.  Add all files to staging: `git add .`
@@ -93,7 +93,7 @@ If there are conflict errors in the tests then we need to make a similar modific
 
 ## Running Commands
 
-To run your modified plugin commands locally, use `./bin/dev` or `./bin/dev.cmd` file, which uses ts-node to execute the plugin's TypeScript commands.
+To run your modified plugin commands locally, use `./bin/dev.js` or `./bin/dev.cmd` file, which uses ts-node to execute the plugin's TypeScript commands.
 
 ```bash
 # Run using local dev file.

DEVELOPING.md

@@ -44,11 +44,11 @@ yarn install
 yarn build
 ```
 
-To use your plugin, run using the local `./bin/dev` or `./bin/dev.cmd` file.
+To use your plugin, run using the local `./bin/dev.js` or `./bin/dev.cmd` file.
 
 ```bash
 # Run using local run file.
-./bin/dev deploy
+./bin/dev.js deploy
 ```
 
 There should be no differences when running via the Salesforce CLI or using the local run file. However, it can be useful to link the plugin to do some additional testing or run your commands from anywhere on your machine.

README.md

@@ -1,3 +1,3 @@
 @echo off
-set NODE_ENV=development
-node "%~dp0\dev" %*
+
+node --loader ts-node/esm --no-warnings=ExperimentalWarning "%~dp0\dev" %*

bin/dev

@@ -0,0 +1,8 @@
+#!/usr/bin/env -S node --loader ts-node/esm --no-warnings=ExperimentalWarning
+// eslint-disable-next-line node/shebang
+async function main() {
+  const { execute } = await import('@oclif/core');
+  await execute({ development: true, dir: import.meta.url });
+}
+
+await main();