Solid Start with Prisma, when making changes to pages results in routing to 404 page.
npx prisma generate and then starting the dev server with npm run dev -- --open. Everything works great. However, I'm having issues with the simpliest of things. If I go into the login form page and add a div element, the entire project breaks. Now instead of seeing a login page when at /login it fashes quickly and then I get the 404 error page. Interestingly, I can edit the names of the fields and that works, it's just when I try to add a new element.
Why is this simple change breaking the project? This is really my first time working with SSR and Prisma for that matter, however I am pretty comfortable using Solid JS. Is there something I am missing? I've tried completely restarting the dev server incase it's an issue with the HMR, but I still get the same behavior....What is the proper way to start solid-start in production (especially with something like pm2)?
solid-start build and then invoking solid-start start.
Is this the proper way to run solid-start in production? ...onCleanup in Root component?
cleaning up root!! message. is there any other way to run code when the app stops/refreshes?
onCleanup(() => {
console.log("cleaning up root!!")
})
onCleanup(() => {
console.log("cleaning up root!!")
})
Now using createResource(), the content never loads.
Access child ref from parent component
`Suspense` deep dive 🐬
Suspense is triggered by throwing a promise. This needs to be done in either the component-body or the jsx, no effects/memos. All code will run until that point. The code throws before anything can mount, nothing runs after the throw: no useEffect and useLayoutEffect, child-components do not run. The suspense-boundary catches the promise and re-renders its children once the promise is resolved.
- ✔️ <Suspense><div>{resource()}</div></Suspense> ...Createeffect not working in component where signal was defined
Replacing specific HTML elements with Solid Components
Render a component referenced by a object
solid start `npm run build` hangs in docker container
npm run build step, at solid-start rendering index.html.... Here is the docker file im using
```dockerfile
FROM node:alpine3.18 AS build
COPY package* ....
server$ API change in start 0.3.1 ?
0.3.1 when I use server$ from an API route endpoint, I get this exception Server function called without a request context? Does this ring bells for some of you?Help with AList Cloud
exclude specific file from getting bundled
How to properly import fonts (with Tailwind)

Resource with createContext?
undefined returned from the useContext call as a function, but if you provide an initial value of () => {} it seems that the context isn't updated reactively when the value createResource accessor is passed to the value prop of the provider?Reactive var in obj
Error handling in dependent memos
Refetching Route Data with Solid Router
@solidjs/router? (not Solid Start; I'm using Vite)
- I'm mutating something on the backend and would like to make sure the data is up to date
- Returning the whole createResource return value kind of works -- calling refetch correctly refetches the data, but mutate doesn't work....SolidStart unicode behavior
