Error when executing esrun through an npm script

[LukenSkyne]

Description:

As the title mentions, I tried using esrun in the npm scripts section. Executing esrun from the shell works like a charm. In the following error output, notice how the path (P:CodingProjectsJSPlayground\n) is missing the backslashes, something related to escaping:

node:internal/errors:490
    ErrorCaptureStackTrace(err);
    ^
> playground@1.0.0 start
TypeError [ERR_INVALID_ARG_VALUE]: The argument 'filename' must be a file URL object, file URL string,
or absolute path string. Received 'P:CodingProjectsJSPlayground\n' +
  'ode_modules.binesrun-clcxt0qmo0000tgfnb0ovcay8.tmp.mjs'
    at new NodeError (node:internal/errors:399:5)
    at createRequire (node:internal/modules/cjs/loader:1356:13)
    at file:///P:/Coding/Projects/JS/Playground/node_modules/.bin/esrun-clcxt0qmo0000tgfnb0ovcay8.tmp.mjs:3:17
    at ModuleJob.run (node:internal/modules/esm/module_job:194:25) {
  code: 'ERR_INVALID_ARG_VALUE'
}

Minimal reproduction steps:

• create a new empty folder
• exectute npm init -y inside of the folder
• install esrun with npm i @digitak/esrun
• add an "example.ts" file (with empty or hello world content)
• add a start script "start": "esrun example.ts" into the scripts section of the package.json
• execute esrun example.ts -> works as expected
• execute npm run start -> error

Tested environments:

Windows 11 Pro

Node:

• 18.13.0
• 19.3.0
• 19.4.0

npm:

• 8.19.3
• 9.3.0

[Gin-Quin]

Alright, I think this is a bug on Windows only. Unfortunately I don't have Windows, but I think I spotted the bug.

Can you try again with the latest version (3.2.16)?

[LukenSkyne]

Yup, 3.2.16 resolves the issue, thanks a lot! ♥