chip902
commented
1 month ago Any error in console, client or Server? I have the same issue but I'm having header problems from the looks of it...
I've used this for my vite config:
import { cloudflareDevProxyVitePlugin as remixCloudflareDevProxy, vitePlugin as remixVitePlugin } from '@remix-run/dev';
import UnoCSS from 'unocss/vite';
import { defineConfig, type ViteDevServer } from 'vite';
import { nodePolyfills } from 'vite-plugin-node-polyfills';
import { optimizeCssModules } from 'vite-plugin-optimize-css-modules';
import tsconfigPaths from 'vite-tsconfig-paths';
export default defineConfig((config) => {
return {
...config,
build: {
target: 'esnext',
},
server: {
headers: {
'Access-Control-Allow-Origin': '*',
'Access-Control-Allow-Methods': 'GET, POST, PUT, DELETE, OPTIONS',
'Access-Control-Allow-Headers': '*'
}
},
plugins: [
{
name: 'add-cors',
configureServer(server) {
server.middlewares.use((_req, res, next) => {
res.setHeader('Cross-Origin-Opener-Policy', 'same-origin');
res.setHeader('Cross-Origin-Embedder-Policy', 'require-corp');
res.setHeader('Cross-Origin-Resource-Policy', 'cross-origin');
res.setHeader('Cross-Origin-Isolated-Policy', 'self');
next();
});
},
},
nodePolyfills({
include: ['path', 'buffer'],
}),
config.mode !== 'test' && remixCloudflareDevProxy(),
remixVitePlugin({
future: {
v3_fetcherPersist: true,
v3_relativeSplatPath: true,
v3_throwAbortReason: true,
},
}),
UnoCSS(),
tsconfigPaths(),
chrome129IssuePlugin(),
config.mode === 'production' && optimizeCssModules({ apply: 'build' }),
],
};
});
function chrome129IssuePlugin() {
return {
name: 'chrome129IssuePlugin',
configureServer(server: ViteDevServer) {
server.middlewares.use((req, res, next) => {
const raw = req.headers['user-agent']?.match(/Chrom(e|ium)\/([0-9]+)\./);
if (raw) {
const version = parseInt(raw[2], 10);
if (version === 129) {
res.setHeader('content-type', 'text/html');
res.end(
'<body><h1>Please use Chrome Canary for testing.</h1><p>Chrome 129 has an issue with JavaScript modules & Vite local development, see <a href="https://github.com/stackblitz/bolt.new/issues/86#issuecomment-2395519258">for more information.</a></p><p><b>Note:</b> This only impacts <u>local development</u>. `pnpm run build` and `pnpm run start` will work fine in this browser.</p></body>',
);
return;
}
}
next();
});
},
};
}
nowjon
drabspirit
WavezeroLLC
lrush85
YAY-3M-TA3
MisterTricky
roly151
RosaiJ
heartsiddharth1
veerababumanyam
Describe the bug
I'm attempting to use some of my local LLMs on Ollama in this fork and everything works great. There aren't any issue with the execution itself. However I'm running into an issue where the code will generate in the chat, but not in the virtual IDE automatically. Its essentially the same thing as if I were to prompt ChatGPT and copy/paste code into my IDE manually. Not sure why this is happening. Tried to debug myself a little and asked some of my LLMs about this issue and didn't have much luck. Hopefully someone can help me resolve this as I'm really excited about the possibility of using local LLMs on Bolt.new. Thank you. :-)
Link to the Bolt URL that caused the error
N/A
Steps to reproduce
Simply followed the Readme that was given step by step.
Expected behavior
To reiterate what I said above, just an issue where the Code and Preview windows don't automatically populate with the LLM generated code. I have tested with multiple LLMs: llama3.2:latest codellama:13b granite-code:20b codellama:34b deepseek-coder-v2:16b codellama:70b
Here is an example of what happens when I try to do a basic example prompt: (here I'm using codellama:13b)
Screen Recording / Screenshot
No response
Platform
Additional context
No response