MobX + SolidJS enableExternalSource untracked bug?
untrack parameter to enableExternalSource I have tried putting MobX's untracked in it, but I'm running into an issue with <For> updates
Please see:
https://github.com/solidjs/solid/issues/1850#issuecomment-1976086047...how to efficiently make nested data structures in solid
SolidStart - Nitro Module missing `context` keys in `request`
Handle user interactions to send backend
How do I use solid for reactivity without a build step?
use directive typescript error
Type '{ type: string; placeholder: string; value: string; "use:test": true; oninput: (e: InputEvent & { currentTarget: HTMLInputElement; target: HTMLInputElement; }) => void; }' is not assignable to type 'InputHTMLAttributes<HTMLInputElement>'.
Property 'use:test' does not exist on type 'InputHTMLAttributes<HTMLInputElement>'.ts(2322)
Type '{ type: string; placeholder: string; value: string; "use:test": true; oninput: (e: InputEvent & { currentTarget: HTMLInputElement; target: HTMLInputElement; }) => void; }' is not assignable to type 'InputHTMLAttributes<HTMLInputElement>'.
Property 'use:test' does not exist on type 'InputHTMLAttributes<HTMLInputElement>'.ts(2322)
I have to fetch initial information in a component, how do I do it?
Dynamically creating resources based on reactive state in Solid Store

Struggling to understand the correct way to use createResource with a store
export const [dataStore, setDataStore] = createStore({ some: "data"}) , which should get populated with data fetched from my api.
In one of my components i want to automatically renavigate to another url if there is an error from the fetch request as the component cant be displayed correctly. For this i wrote this:
```const [data, setData] = createResource<any, any>(fetchData)
...How do I "protect" routes? I am using @solidjs/router
What are canonical patterns to separate UI from domain logic in SolidJS?
solidjs createResource doesn't show error when there was an error i.e 401 Invalid credentials
someone used the plugin postcss-functions ?
Hydration Mismatch. Unable to find DOM nodes for hydration key
@fastify/vite plugin. I've finally got something rendering, but am getting this error:
```
Uncaught Error: Hydration Mismatch. Unable to find DOM nodes for hydration key: 0-0
at getNextElement (chunk-TJVPM3FD.js?v=ff79f117:398:13)
at _$$component.location (App.tsx:8:2)...solid primitives storage is bug
memo with dynamic props pass
Pass authed user data to protected routes
AWS Amplify with SSR Solid Start
Why is it considered wrong to destruct props?
If I am using a singleton class why would I use a context