Open danielniccoli opened 1 month ago
I accidentally ran bun run build
from a child directory. When running it from the project root directory, it works. I am not sure if this is intentional. But since it is meant to be a drop-in replacement for npm, and the npm command from that same child directory works, I'll leave this issue open for review.
before you run bun run build
, delete the build directory. SK outputs the build files in the folder build
and when you run bun run build
bun wants to run the files in build
instead of the script build
defined in your package json.
So either delete the folder each time before you run build
or rename the script to something else.
before you run
bun run build
, delete the build directory. SK outputs the build files in the folderbuild
and when you runbun run build
bun wants to run the files inbuild
instead of the scriptbuild
defined in your package json.So either delete the folder each time before you run
build
or rename the script to something else.
No, that's not the cause. The issue is reproducible whether or not the build folder exists. It's purely related to the path from where I run bun run build
.
What version of Bun is running?
1.1.26+0a37423ba
What platform is your computer?
Microsoft Windows NT 10.0.22631.0 x64
What steps can reproduce the bug?
bun run build
What is the expected behavior?
This is what I get with
npm run build
. I expect a successful build step with bun, too.What do you see instead?
Additional information
package.json