fix: use node versus ts-node to run scripts

forcedotcom · Dec 8, 2023 · 7c37ad0 · 7c37ad0
1 parent 5c5a1b4
commit 7c37ad0
Showing 1 changed file with 2 additions and 1 deletion.
diff --git a/utils/sf-config.js b/utils/sf-config.js
@@ -93,7 +93,8 @@ const resolveConfig = (path) => {
 
   // if path is undefined/null, assume we're executing from a plugin root
   const usesJsBinScripts = existsSync(join(path ?? process.cwd(), 'bin', 'dev.js'));
-  const dev = usesJsBinScripts ? 'ts-node "./bin/dev.js"' : '"./bin/dev"';
+  const loader = 'node --loader ts-node/esm --no-warnings=ExperimentalWarning';
+  const dev = usesJsBinScripts ? `${loader} "./bin/dev.js"` : '"./bin/dev"';
   const pluginDefaults = {
     scripts: {
       ...PACKAGE_DEFAULTS.scripts,