You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Doing a crash course in solid by porting a site to solidstart. I know very little about any of these frameworks. I went with the solidstart guide and used that to create a dev container. I also installed the solid browser extension. Everything seems okay until I check the browser console:
[vite] server connection lost. Polling for restart...
client:732 GET http://localhost:42093/_build/ net::ERR_CONNECTION_REFUSED client:732
The port number logged to console is always random regardless of what I set in vite.config.js:
import { defineConfig } from 'vite'import solid from 'vite-plugin-solid' // or solid-start/viteimport devtools from 'solid-devtools/vite'export default defineConfig({server: {strictPort: true,host: "127.0.0.1",port: 3002,hmr: {// host: "127.0.0.1",port: 3002,// clientPort: 3002,},},plugins: [devtools({/* features options - all disabled by default */locator: {targetIDE: 'vscode',componentLocation: true,jsxLocation: true,},autoname: true, // e.g. enable autoname}),solid({// currently HMR breaks displaying components// https://github.com/solidjs/solid-refresh/pull/41 will fix thishot: false,}),],})
The two ports actually open are 3000 (main) and 3001 (For the browser extension). Both are exposed on the host and the extension is able to connect.
Doing a crash course in solid by porting a site to solidstart. I know very little about any of these frameworks. I went with the solidstart guide and used that to create a dev container. I also installed the solid browser extension. Everything seems okay until I check the browser console:
The port number logged to console is always random regardless of what I set in vite.config.js:
The two ports actually open are 3000 (main) and 3001 (For the browser extension). Both are exposed on the host and the extension is able to connect.
package.json:
potentially related to: vitejs/vite#4259
The text was updated successfully, but these errors were encountered: