Damian Tarnawski

That would be awesome 😎 I've already made the [solid devtools frontend as a separate package](https://github.com/thetarnav/solid-devtools/tree/main/packages/frontend#readme) and it works great. So I only need a debugger running on the page,...

Changed in solid in https://github.com/solidjs/solid/pull/1460

@luy19 works great, thanks! I had to add one more file though: `node_modules/solid-start/islands/router.ts` And here is the whole project for reference: https://github.com/solidjs-community/solid.new

imo both `readonly T[]` and `T[]` should behave the same If an array has type `readonly T[]` it doesn't mean that it includes ALL of `T` in it for the...

just hit the same issue code ```odin package bug import "core:fmt" VAL: [3]u8 : {1, 2, 3} arr: [69][3]u8 = VAL main :: proc() { fmt.println(arr) } ``` output ```...

Combining `` with `lazy` should be enough to drop the code, right? As a component, it can be easily composed. ```tsx const MyLazyComponent = lazy(() => import("...")) ```

Yeah, the issue is mostly about the order of `onCleanup` calls in dev vs prod. Probably should be titled better.

I think the question is less about typescript itself and more about what users are supposed to do — handle that case or not?. It might be "fine" to not,...

I agree that reading context anywhere but in component body is usually a bad practice. But I have a good reason for this, I'm working on a i18n library that...

Interesting I've removed all export conditions from dependencies and decided to just rely on `isServer` exported by solid, but as it turns out, `isServer` is different when imported in a...