Channels
Getting Object.hasOwn is not a function on older browsers. Attaching the trace
Style attribute not updating in Safari
style
attribute is not updating. I've got it down to
<div data-foo={`width: ${width()}`} style={`width: ${width()}`}>
<div data-foo={`width: ${width()}`} style={`width: ${width()}`}>
Server Actions and Cookies sending error: Cannot set headers after they are sent to the clien
how to use bun:sqlite without it leaking to the browser?
Solid +Astro SSR + Data Fetching on hydration
Is it ok to use a global store to persist component state between mounts?
Solid Start (experiments) nested layout
Solid Start (experiments) nested layout
Kobalte 13.x update issue
Tagged Template Literals - Why is unwrapped props value reactive?
API route in Route Group not picked up?
npm init solid@latest
and create the file apiget.ts
```JSX
export function GET() {
return new Response('Hello World');...computations created outside a `createRoot` or `render` will never be disposed
keydown
event attached to the document.
```..."AsyncLocalStorage" is not exported by "__vite-browser-external"
npm run build
dies with ../node_modules/vinxi/runtime/http.js (70:9): "AsyncLocalStorage" is not exported by "__vite-browser-external", imported by "../node_modules/vinxi/runtime/http.js"
Any suggestions on how to fix it up? Using node v20.12.2...About tracking re-renders and Store usage
Get the request header inside a form action? For Solid Start
“Push synchronization to the edge of the reactive graph”
Router preload and cache.set don't seem to be working
Is this (completely 🫣) illegal in Solid world?
Calling root render multiple times
root.render(<App someProp={43}/>
), React will update the DOM as necessary to reflect the latest JSX you passed. Calling render on the same root again is similar to calling the set function on the root component.
What's the suggested way to achieve a similar behavior using solid render(() => <App />, document.getElementById("app"));
?...Vite 5.2.x / Vitest 1.5.x: How to Resolve Multiple Instances of Solid
@solidjs/testing-library
and vitest
```
stderr | file:~/Developer/github/.../nm/node_modules/solid-js/dist/dev.js:1932:13
You appear to have multiple instances of Solid. This can lead to unexpected behavior....