starred/cloudbeaver

Fork 0

mirror of https://github.com/dbeaver/cloudbeaver.git synced 2026-04-26 06:06:00 +03:00

[GH-ISSUE #3534] Running build-frontend.sh #1276

New issue

Closed

opened 2026-03-07 21:01:59 +03:00 by kerem · 7 comments

kerem commented

2026-03-07 21:01:59 +03:00

Owner

Originally created by @mickelelkhoury on GitHub (Jun 19, 2025).
Original GitHub issue: https://github.com/dbeaver/cloudbeaver/issues/3534

Originally assigned to: @Wroud on GitHub.

Hi,

I have been trying to run the build-frontend.sh and am running into an issue where even tho I am using yarn 4.6.0
When it runs yarn install --immutable, it complains, saying I tried to change the lock file

Now after I removed the --immutable the build will pass, but when I run the container locally, I will get stuck on the loading page of the webapp and not run as expected.

The steps I usually took when doing this with earlier versions were:
run build.sh (which is running build backend and frontend), then I run make-docker-container.sh then run-docker-container.sh

Can anyone assist with the yarn thing. am IO using a wrong version or maybe a step I'm missing before running the frontend build file

Originally created by @mickelelkhoury on GitHub (Jun 19, 2025). Original GitHub issue: https://github.com/dbeaver/cloudbeaver/issues/3534 Originally assigned to: @Wroud on GitHub. Hi, I have been trying to run the build-frontend.sh and am running into an issue where even tho I am using yarn 4.6.0 When it runs `yarn install --immutable`, it complains, saying I tried to change the lock file Now after I removed the `--immutable` the build will pass, but when I run the container locally, I will get stuck on the loading page of the webapp and not run as expected. The steps I usually took when doing this with earlier versions were: run build.sh (which is running build backend and frontend), then I run make-docker-container.sh then run-docker-container.sh Can anyone assist with the yarn thing. am IO using a wrong version or maybe a step I'm missing before running the frontend build file

kerem

2026-03-07 21:01:59 +03:00

closed this issue
added the
deployment

wait for response
labels

kerem commented

2026-03-07 21:02:00 +03:00

Author

Owner

@EvgeniaBzzz commented on GitHub (Jun 19, 2025):

It looks like you have some outdated artifacts left in the cloudbeaver/common-react folder that no longer exist in the current version of the repository. That’s likely causing the issue during the build.

You can fix it in one of two ways:

Do a hard reset inside the common-react folder to discard any local changes:

cd cloudbeaver/common-react
git reset --hard

Alternatively, you can clone the repository from scratch, or just clone it to a new location and copy the clean common-react folder over your current one.

Let me know if that helps.

@EvgeniaBzzz commented on GitHub (Jun 19, 2025): It looks like you have some outdated artifacts left in the cloudbeaver/common-react folder that no longer exist in the current version of the repository. That’s likely causing the issue during the build. You can fix it in one of two ways: 1. Do a hard reset inside the common-react folder to discard any local changes: ``` cd cloudbeaver/common-react git reset --hard ``` 2. Alternatively, you can clone the repository from scratch, or just clone it to a new location and copy the clean common-react folder over your current one. Let me know if that helps.

kerem commented

2026-03-07 21:02:01 +03:00

Author

Owner

@mickelelkhoury commented on GitHub (Jun 20, 2025):

Using a new clone of the repo and running it using jdk 21 and yarn 4.6.0.

I am not aiming to change any of the frontend I just need to run the build.sh file and for it to compile so I can run an image on my machine.

when I run it the backend compiles fine

[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  01:21 min
[INFO] Finished at: 2025-06-20T11:14:42+03:00
[INFO] ------------------------------------------------------------------------

but when it comes to the frotend step I keep on getting this error:

➤ YN0000: · Yarn 4.6.0
➤ YN0000: ┌ Resolution step
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
➤ YN0000: └ Completed
➤ YN0000: ┌ Link step
➤ YN0000: │ ESM support for PnP uses the experimental loader API and is therefore experimental
➤ YN0007: │ @parcel/watcher@npm:2.5.1 must be built because it never has been before or the last one failed
➤ YN0007: │ esbuild@npm:0.25.4 must be built because it never has been before or the last one failed
➤ YN0000: └ Completed in 0s 731ms
➤ YN0000: · Done with warnings in 1s 69ms
➤ YN0000: · Yarn 4.6.0
➤ YN0000: ┌ Resolution step
➤ YN0085: │ + react-data-grid@file:./artifacts#./artifacts::hash=9aa799&locator=%40dbeaver%2Freact-data-grid%40workspace%3A..%2Fcommon-react%2F%40dbeaver%2Freact-data-grid
➤ YN0085: │ - react-data-grid@file:./artifacts#./artifacts::hash=2f312f&locator=%40dbeaver%2Freact-data-grid%40workspace%3A..%2Fcommon-react%2F%40dbeaver%2Freact-data-grid
➤ YN0000: └ Completed in 0s 274ms
➤ YN0000: ┌ Post-resolution validation
➤ YN0060: │ graphql-request is listed by your project with version 7.1.2 (p07705), which doesn't satisfy what @graphql-codegen/typescript-graphql-request requests (^6.0.0).
➤ YN0060: │ react is listed by your project with version 19.1.0 (p008c4), which doesn't satisfy what reakit and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ react is listed by your project with version 19.1.0 (p641f8), which doesn't satisfy what reakit and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ react is listed by your project with version 19.1.0 (p685f4), which doesn't satisfy what react-inspector (via @ladle/react) and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ react is listed by your project with version 19.1.0 (p8db15), which doesn't satisfy what go-split and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ react is listed by your project with version 19.1.0 (p8e979), which doesn't satisfy what react-popper and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ react is listed by your project with version 19.1.0 (p9149d), which doesn't satisfy what reakit and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ react is listed by your project with version 19.1.0 (pd98f3), which doesn't satisfy what reakit and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ react is listed by your project with version 19.1.0 (pf3b50), which doesn't satisfy what reakit and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ react-dom is listed by your project with version 19.1.0 (p1798b), which doesn't satisfy what go-split and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ react-dom is listed by your project with version 19.1.0 (p2308c), which doesn't satisfy what react-popper and other dependencies request (^16.8.0 || ^17.0.0 || ^18.0.0).
➤ YN0060: │ react-dom is listed by your project with version 19.1.0 (p262e0), which doesn't satisfy what reakit and other dependencies request (^16.8.0 || ^17.0.0).
➤ YN0060: │ react-dom is listed by your project with version 19.1.0 (p2a477), which doesn't satisfy what reakit and other dependencies request (^16.8.0 || ^17.0.0).
➤ YN0060: │ react-dom is listed by your project with version 19.1.0 (p2b288), which doesn't satisfy what reakit and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ react-dom is listed by your project with version 19.1.0 (paaac8), which doesn't satisfy what reakit and other dependencies request (^16.8.0 || ^17.0.0).
➤ YN0060: │ react-dom is listed by your project with version 19.1.0 (pdbae7), which doesn't satisfy what reakit and other dependencies request (^16.8.0 || ^17.0.0).
➤ YN0002: │ @cloudbeaver/core-blocks@workspace:packages/core-blocks doesn't provide @testing-library/dom (p71190), requested by @testing-library/react.
➤ YN0002: │ @cloudbeaver/eslint-config@workspace:packages/eslint-config doesn't provide typescript (p857be), requested by @typescript-eslint/eslint-plugin and other dependencies.
➤ YN0002: │ @cloudbeaver/plugin-help@workspace:packages/plugin-help doesn't provide mobx (p1f834), requested by mobx-react-lite.
➤ YN0086: │ Some peer dependencies are incorrectly met by your project; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code.
➤ YN0086: │ Some peer dependencies are incorrectly met by dependencies; run yarn explain peer-requirements for details.
➤ YN0000: │ 
➤ YN0000: │ @@ -15841,15 +15841,14 @@
➤ YN0000: │    linkType: hard
➤ YN0000: │
➤ YN0000: │  "react-data-grid@file:./artifacts::locator=%40dbeaver%2Freact-data-grid%40workspace%3A..%2Fcommon-react%2F%40dbeaver%2Freact-data-grid":
➤ YN0000: │    version: 7.0.0-beta.55
➤ YN0028: │ -  resolution: "react-data-grid@file:./artifacts#./artifacts::hash=2f312f&locator=%40dbeaver%2Freact-data-grid%40workspace%3A..%2Fcommon-react%2F%40dbeaver%2Freact-data-grid"
➤ YN0028: │ +  resolution: "react-data-grid@file:./artifacts#./artifacts::hash=9aa799&locator=%40dbeaver%2Freact-data-grid%40workspace%3A..%2Fcommon-react%2F%40dbeaver%2Freact-data-grid"
➤ YN0000: │    dependencies:
➤ YN0000: │      clsx: "npm:^2.0.0"
➤ YN0000: │    peerDependencies:
➤ YN0000: │      react: ^19.0
➤ YN0000: │      react-dom: ^19.0
➤ YN0028: │ -  checksum: 10c0/f0f3685c1ebcd3e0d3f33f189016a541eee963db1beb3f751209ef6eeb39497a08e1a583900a42a596b017e5daf6935d9ab9cd444e3b16ed905399e941eeadbb
➤ YN0000: │    languageName: node
➤ YN0000: │    linkType: hard
➤ YN0000: │
➤ YN0000: │  "react-dnd-html5-backend@npm:^16":
➤ YN0000: │
➤ YN0028: │ The lockfile would have been modified by this install, which is explicitly forbidden.
➤ YN0000: └ Completed
➤ YN0000: · Failed with errors in 0s 350ms

Note that this is right after running a clean clone, I have 0 changes

@mickelelkhoury commented on GitHub (Jun 20, 2025): Using a new clone of the repo and running it using jdk 21 and yarn 4.6.0. I am not aiming to change any of the frontend I just need to run the build.sh file and for it to compile so I can run an image on my machine. when I run it the backend compiles fine ```[INFO] CloudBeaver CE Aggregate 1.0.0-SNAPSHOT ............ SUCCESS [ 0.015 s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 01:21 min [INFO] Finished at: 2025-06-20T11:14:42+03:00 [INFO] ------------------------------------------------------------------------ ``` but when it comes to the frotend step I keep on getting this error: ```Build static content ➤ YN0000: · Yarn 4.6.0 ➤ YN0000: ┌ Resolution step ➤ YN0000: └ Completed ➤ YN0000: ┌ Fetch step ➤ YN0000: └ Completed ➤ YN0000: ┌ Link step ➤ YN0000: │ ESM support for PnP uses the experimental loader API and is therefore experimental ➤ YN0007: │ @parcel/watcher@npm:2.5.1 must be built because it never has been before or the last one failed ➤ YN0007: │ esbuild@npm:0.25.4 must be built because it never has been before or the last one failed ➤ YN0000: └ Completed in 0s 731ms ➤ YN0000: · Done with warnings in 1s 69ms ➤ YN0000: · Yarn 4.6.0 ➤ YN0000: ┌ Resolution step ➤ YN0085: │ + react-data-grid@file:./artifacts#./artifacts::hash=9aa799&locator=%40dbeaver%2Freact-data-grid%40workspace%3A..%2Fcommon-react%2F%40dbeaver%2Freact-data-grid ➤ YN0085: │ - react-data-grid@file:./artifacts#./artifacts::hash=2f312f&locator=%40dbeaver%2Freact-data-grid%40workspace%3A..%2Fcommon-react%2F%40dbeaver%2Freact-data-grid ➤ YN0000: └ Completed in 0s 274ms ➤ YN0000: ┌ Post-resolution validation ➤ YN0060: │ graphql-request is listed by your project with version 7.1.2 (p07705), which doesn't satisfy what @graphql-codegen/typescript-graphql-request requests (^6.0.0). ➤ YN0060: │ react is listed by your project with version 19.1.0 (p008c4), which doesn't satisfy what reakit and other dependencies request (but they have non-overlapping ranges!). ➤ YN0060: │ react is listed by your project with version 19.1.0 (p641f8), which doesn't satisfy what reakit and other dependencies request (but they have non-overlapping ranges!). ➤ YN0060: │ react is listed by your project with version 19.1.0 (p685f4), which doesn't satisfy what react-inspector (via @ladle/react) and other dependencies request (but they have non-overlapping ranges!). ➤ YN0060: │ react is listed by your project with version 19.1.0 (p8db15), which doesn't satisfy what go-split and other dependencies request (but they have non-overlapping ranges!). ➤ YN0060: │ react is listed by your project with version 19.1.0 (p8e979), which doesn't satisfy what react-popper and other dependencies request (but they have non-overlapping ranges!). ➤ YN0060: │ react is listed by your project with version 19.1.0 (p9149d), which doesn't satisfy what reakit and other dependencies request (but they have non-overlapping ranges!). ➤ YN0060: │ react is listed by your project with version 19.1.0 (pd98f3), which doesn't satisfy what reakit and other dependencies request (but they have non-overlapping ranges!). ➤ YN0060: │ react is listed by your project with version 19.1.0 (pf3b50), which doesn't satisfy what reakit and other dependencies request (but they have non-overlapping ranges!). ➤ YN0060: │ react-dom is listed by your project with version 19.1.0 (p1798b), which doesn't satisfy what go-split and other dependencies request (but they have non-overlapping ranges!). ➤ YN0060: │ react-dom is listed by your project with version 19.1.0 (p2308c), which doesn't satisfy what react-popper and other dependencies request (^16.8.0 || ^17.0.0 || ^18.0.0). ➤ YN0060: │ react-dom is listed by your project with version 19.1.0 (p262e0), which doesn't satisfy what reakit and other dependencies request (^16.8.0 || ^17.0.0). ➤ YN0060: │ react-dom is listed by your project with version 19.1.0 (p2a477), which doesn't satisfy what reakit and other dependencies request (^16.8.0 || ^17.0.0). ➤ YN0060: │ react-dom is listed by your project with version 19.1.0 (p2b288), which doesn't satisfy what reakit and other dependencies request (but they have non-overlapping ranges!). ➤ YN0060: │ react-dom is listed by your project with version 19.1.0 (paaac8), which doesn't satisfy what reakit and other dependencies request (^16.8.0 || ^17.0.0). ➤ YN0060: │ react-dom is listed by your project with version 19.1.0 (pdbae7), which doesn't satisfy what reakit and other dependencies request (^16.8.0 || ^17.0.0). ➤ YN0002: │ @cloudbeaver/core-blocks@workspace:packages/core-blocks doesn't provide @testing-library/dom (p71190), requested by @testing-library/react. ➤ YN0002: │ @cloudbeaver/eslint-config@workspace:packages/eslint-config doesn't provide typescript (p857be), requested by @typescript-eslint/eslint-plugin and other dependencies. ➤ YN0002: │ @cloudbeaver/plugin-help@workspace:packages/plugin-help doesn't provide mobx (p1f834), requested by mobx-react-lite. ➤ YN0086: │ Some peer dependencies are incorrectly met by your project; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code. ➤ YN0086: │ Some peer dependencies are incorrectly met by dependencies; run yarn explain peer-requirements for details. ➤ YN0000: │ ➤ YN0000: │ @@ -15841,15 +15841,14 @@ ➤ YN0000: │ linkType: hard ➤ YN0000: │ ➤ YN0000: │ "react-data-grid@file:./artifacts::locator=%40dbeaver%2Freact-data-grid%40workspace%3A..%2Fcommon-react%2F%40dbeaver%2Freact-data-grid": ➤ YN0000: │ version: 7.0.0-beta.55 ➤ YN0028: │ - resolution: "react-data-grid@file:./artifacts#./artifacts::hash=2f312f&locator=%40dbeaver%2Freact-data-grid%40workspace%3A..%2Fcommon-react%2F%40dbeaver%2Freact-data-grid" ➤ YN0028: │ + resolution: "react-data-grid@file:./artifacts#./artifacts::hash=9aa799&locator=%40dbeaver%2Freact-data-grid%40workspace%3A..%2Fcommon-react%2F%40dbeaver%2Freact-data-grid" ➤ YN0000: │ dependencies: ➤ YN0000: │ clsx: "npm:^2.0.0" ➤ YN0000: │ peerDependencies: ➤ YN0000: │ react: ^19.0 ➤ YN0000: │ react-dom: ^19.0 ➤ YN0028: │ - checksum: 10c0/f0f3685c1ebcd3e0d3f33f189016a541eee963db1beb3f751209ef6eeb39497a08e1a583900a42a596b017e5daf6935d9ab9cd444e3b16ed905399e941eeadbb ➤ YN0000: │ languageName: node ➤ YN0000: │ linkType: hard ➤ YN0000: │ ➤ YN0000: │ "react-dnd-html5-backend@npm:^16": ➤ YN0000: │ ➤ YN0028: │ The lockfile would have been modified by this install, which is explicitly forbidden. ➤ YN0000: └ Completed ➤ YN0000: · Failed with errors in 0s 350ms ``` Note that this is right after running a clean clone, I have 0 changes

kerem commented

2026-03-07 21:02:01 +03:00

Author

Owner

@Wroud commented on GitHub (Jun 20, 2025):

@mickelelkhoury, can you please tell me what OS you are using?

@Wroud commented on GitHub (Jun 20, 2025): @mickelelkhoury, can you please tell me what OS you are using?

kerem commented

2026-03-07 21:02:01 +03:00

Author

Owner

@EvgeniaBzzz commented on GitHub (Jul 17, 2025):

@mickelelkhoury any news here?

@EvgeniaBzzz commented on GitHub (Jul 17, 2025): @mickelelkhoury any news here?

kerem commented

2026-03-07 21:02:01 +03:00

Author

Owner

@EvgeniaBzzz commented on GitHub (Oct 2, 2025):

Let us know if this issue is still actual for you.

@EvgeniaBzzz commented on GitHub (Oct 2, 2025): Let us know if this issue is still actual for you.

kerem commented

2026-03-07 21:02:01 +03:00

Author

Owner

@mickelelkhoury commented on GitHub (Oct 9, 2025):

Hello,
It did work.
I am doing that again today and running into the same issue
What I remember is that when I run the build-frontend for some reason, because of the yarn install --immutable it's complaining about

➤ YN0028: │ +  resolution: "react-data-grid@file:./artifacts#./artifacts::hash=9aa799&locator=%40dbeaver%2Freact-data-grid%40workspace%3A%40dbeaver%2Freact-data-grid"

when running it.
Now removing the --immutable allows me to run build-frontend.sh
and everything works fine

@mickelelkhoury commented on GitHub (Oct 9, 2025): Hello, It did work. I am doing that again today and running into the same issue What I remember is that when I run the build-frontend for some reason, because of the `yarn install --immutable` it's complaining about ``` - resolution: "react-data-grid@file:./artifacts#./artifacts::hash=2f312f&locator=%40dbeaver%2Freact-data-grid%40workspace%3A%40dbeaver%2Freact-data-grid" ➤ YN0028: │ + resolution: "react-data-grid@file:./artifacts#./artifacts::hash=9aa799&locator=%40dbeaver%2Freact-data-grid%40workspace%3A%40dbeaver%2Freact-data-grid" ``` when running it. Now removing the --immutable allows me to run build-frontend.sh and everything works fine

kerem commented

2026-03-07 21:02:01 +03:00

Author

Owner

@mickelelkhoury commented on GitHub (Oct 9, 2025):

@mickelelkhoury, can you please tell me what OS you are using?

Windows 11

@mickelelkhoury commented on GitHub (Oct 9, 2025): > [@mickelelkhoury](https://github.com/mickelelkhoury), can you please tell me what OS you are using? Windows 11

kerem referenced this issue

2026-03-07 21:08:39 +03:00

[PR #1276] [MERGED] Cb 2337 users table filtering #2377