Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bun breaks deploy #277

Closed
justin-hackin opened this issue Mar 29, 2024 · 2 comments
Closed

bun breaks deploy #277

justin-hackin opened this issue Mar 29, 2024 · 2 comments

Comments

@justin-hackin
Copy link

Have you experienced this bug with the latest version of the template?

Yes

Steps to Reproduce

just run bun i in a fresh template derivation and push it out, you will see the action fail, complaining about lockfile:

#10 [production-deps 3/4] ADD package.json package-lock.json .npmrc ./
#10 ERROR: failed to calculate checksum of [REDACTED]: "/package-lock.json": not found

#11 [deps 2/3] ADD package.json package-lock.json .npmrc ./
#11 ERROR: failed to calculate checksum of  [REDACTED]: "/package-lock.json": not found
------
 > [deps 2/3] ADD package.json package-lock.json .npmrc ./:
------
------
 > [production-deps 3/4] ADD package.json package-lock.json .npmrc ./:
------
Error: failed to fetch an image or build from source: error building: failed to solve: failed to compute cache key: failed to calculate checksum of [REDACTED]: "/package-lock.json": not found
Error: Process completed with exit code 1.

Expected Behavior

The deploy is successful

Actual Behavior

The deploy fails

@mcansh
Copy link
Contributor

mcansh commented Mar 30, 2024

change package-lock.json usages in the dockerfile to bun.lockb and update npm i usage to bun i and it should be good to go

@justin-hackin
Copy link
Author

Okay I see that the init script detects package manager, whoops, thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants