Bug in current main branch

bolt.diy [bolt.diy] Issues and Troubleshooting
1

The current main branch cant be run (npm run dev):

> bolt@ dev bolt.new-any-llm
> node pre-start.cjs;  remix vite:dev

node:internal/modules/cjs/loader:1242
  throw err;
  ^

Error: Cannot find module 'bolt.new-any-llm\pre-start.cjs;'
    at Function._resolveFilename (node:internal/modules/cjs/loader:1239:15)
    at Function._load (node:internal/modules/cjs/loader:1064:27)
    at TracingChannel.traceSync (node:diagnostics_channel:322:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:218:24)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:170:5)
    at node:internal/main/run_main_module:36:49 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v23.3.0
 ELIFECYCLE  Command failed with exit code 1.

Fix => package.json => remove semicolon, replace with " &&"

image
image1009×477 33.8 KB

2 Likes
2

Made this change but there’s still some issues.

This probably isn’t the desired output. Even if I update the .env file, I still get the message:

image

image
image1920×1080 176 KB

And I get a bunch of console (DOM) errors for Check the render method of "SlotClone". and (x) > GET http://localhost:1234/v1/models net::ERR_CONNECTION_REFUSED WARN Constants Failed to get LMStudio models: Failed to fetch

image
image1920×1080 217 KB

But everything arguably still works.

We need a development or testing branch with merged changes. These were definitely breaking changes, but to be fair I’ve been getting the Ollama warnings forever (all versions).

P.S. And I’m not using local models or have any settings defined for them.

3

For me it was not working and showing no providers are present as mentioned in another topic here to. Also the same error in console as you got.

I think this commit makes the problem here:

If I change it back from && to || in line 26

1 Like
4

Please disregard the bit about the providers. I see I have to literally change this in the settings now, which is fine. But maybe would be best to have it default to the .env if present? A little less misleading in some cases.

Love the settings feature now though!!

And can we get rid of that Ollama check if not being set? lol

Just an FYI, but I would expect to be able to set the keys in “Providers” under settings, not to just filter by the one’s selected (I personally think we should extract the PROVIDER_LIST from the constants.ts and make it a JSON file which then gets called and compiled).

And maybe there’s a better place to make suggestions on UI/UX?

5

about the settings just clear the cache and test it.
by default it should have all the providers working

6

If I change it back from && to || in line 26

this will break the changes as if you keep a provider false it will never stay false

7

please repull the repo, this is fixed now

also added a fix for the default settings for provider

you can pull the changes now

2 Likes
8

Thanks, that works :slight_smile:

2 Likes