Package.json backslash escaping is not consistent with Node.JS's

wundersolutions-juanjo commented 3 months ago

What version of Bun is running?

1.1.13+bd6a60512

What platform is your computer?

Microsoft Windows NT 10.0.19045.0 x64

What steps can reproduce the bug?

Create a package.json with a start script that uses escaped backslashes
- For example, "start": "bun C:\\NodeExpressServer\\server.js ./www"
Run the script with bun run start
- For the provided example, I get the error error: Module not found "C:NodeExpressServerserver.js"
- Using npm run start takes it's time, but eventually runs fine :P

What is the expected behavior?

bun run should be consistent with npm run

What do you see instead?

For the provided example, bun run requires another "round" of escaping backslashes, turning it into "start": "bun C:\\\\NodeExpressServer\\\\server.js ./www"

Additional information

No response

museadam commented 2 months ago

Try using the forward slash '/' instead

Or you can also create a bash/powershell script to run the command bun C:\\NodeExpressServer\\server.js ./www to start your server

stefreak commented 1 month ago

This is not a windows issue, it also happens on other platforms and can be very confusing.

This is also a security problem, as it makes it impossible to use double quotes to prevent shell injection in the package.json script

oven-sh / bun