[Bug]: `Component Bar Charts Not Found` after upgrading to `lowcoder-ce:2.7.5`

[nguyenmp]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

On 2.7.5, Bar Charts and Openlayer Geomaps do not load properly. Simple components, such as List View, work fine.

They display Error: Component barChart Not Found. and Error: Component geo Not Found.

There's a dependency on http://localhost:3000/api/npm/package/68fc4d3431a7a770d72b60c1/lowcoder-comps@latest/index.js that errors out with HTTP 500:

{"code":5000,"message":"Oops! Service is busy, please try again later.","success":false}

Expected Behavior

On 2.7.4, I was able to add Bar Charts and Openlayer Geomaps.

I could visit http://localhost:3000/api/npm/package/68fc49d1a2d0b629500e4725/lowcoder-comps@2.7.5/index.js and get the proper JavaScript.

Steps to reproduce

1. Run docker run -d --name lowcoder -p 3000:3000 lowcoderorg/lowcoder-ce:2.7.5
2. Visit localhost:3000
3. Register a new user
4. Create a new app
5. Add a Bar Chart and a Openlayers Geomap. These components are broken.
6. Kill the process and rerun with 2.7.4 and see everything work

Environment

I think error was introduced in lowcoder-ce 2.7.5. Downgrading to 2.7.4 works around the issue.

MacOS running Docker Desktop, but I also reproduced this originally on Linux Docker.

Additional Information

In my logs, I see the API service running so I'm surprised it's replying as unavailable:

2025-10-25 03:05:39,402 INFO success: redis entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2025-10-25 03:05:49,479 INFO success: mongodb entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)

2025-10-25 03:05:49,479 INFO success: api-service entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)

2025-10-25 03:05:49,479 INFO success: frontend entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)

2025-10-25 03:05:49,479 INFO success: node-service entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)