Skip to content

chore: Regenerate bun lockfile - #740

Closed
Sanielia wants to merge 1 commit into
masterfrom
chore/regenerate-lockfile
Closed

chore: Regenerate bun lockfile#740
Sanielia wants to merge 1 commit into
masterfrom
chore/regenerate-lockfile

Conversation

@Sanielia

Copy link
Copy Markdown
Member

Currently our bun.lock is generated with bun version 1.3.2, I base this information on fact that in line 3 there is configVersion: 0, whereas configVersion property was added in bun 1.3.1.

If I run bun install on master it removes this property, however it causes problems with building (it cannot resolve vue while importing it). Running it with frozen-lockfile doesn't remove the configVersion, runs properly without errors and doesn't pose any problems when building, however on #731 even running it with frozen-lockfile messes up build. Regenerating bun lockfile from scratch fixes this problem.

What should also be done in this pr is assuring that renovate uses same bun version as this project when updating deps, therefore this is WIP

@hack4krak-deployment

hack4krak-deployment Bot commented Nov 17, 2025

Copy link
Copy Markdown

Dokploy Preview Deployment

Name Status Preview Updated (UTC)
Frontend ✅ Done Preview URL 2025-11-17T18:18:20.982Z

@Sanielia

Copy link
Copy Markdown
Member Author

erm it passes locally and in docker…

@Sanielia

Copy link
Copy Markdown
Member Author

as bun update has been merge it is no longer required, also #744 has been created

@Sanielia Sanielia closed this Nov 23, 2025
@Sanielia
Sanielia deleted the chore/regenerate-lockfile branch February 19, 2026 10:34
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

Successfully merging this pull request may close these issues.

1 participant