My current guesses: it halts or it does not halt
I've narrowed it down to two possible answers
I consume my photons raw, straight from the source.
One use case for the new `JSON.parse` source API: adding custom handling for floating point rounding (e.g. error or switch to BigInt):
proposal: github.com/tc39/proposa...
mdn: developer.mozilla.org/en-US/docs/W...
1000s of optimistic lanes here we come!
thanks for the stackBlitz that's very helpful.
I was trying to get an understanding of the core signal primitives that would sync the effects that UI rendering would then be built on top of but looks like effects set to 'render' mode _are_ the primitive.
Ah I was just using createTrackedEffect as I was being lazy. I really like that the createEffect API is split by default - I was worrying about signal reads throwing between real side effects and forcing the split is a nice solution
I changed the import map to point to 2
I was having fun playing around with the new APIs. I was expecting this code to not "tear" and the slower effect would also hold up the faster effect. But that's not what I'm seeing.
Looks like I need to use an async action to hold up all deps of a value?
playground.solidjs.com/anonymous/8a...
I spot a @johnnyreilly.com in his natural habitat (by the Thames)
I don't think there is a mapping page. Under the hood it uses amaro, which is a wrapper around swc.
So to know if certain syntax is supported you'll need to work backwards from when it was added to swc.
Yeah import extensions are the main complexity there. As still nice to be able to run the `.ts` directly during `--test`.
As long as you're using the right versions of Node.js yeah! It follows the same approach as ts-blank-space, replacing type annotations with whitespace.
nodejs.org/api/module.h...
If anyone needs a silly, not portable, zero dependency, one liner TypeScript build script that can only handle a single file. Look no further!
The other day I had an AI saying that there was no such thing as Date.prototype.toTemporalInstant.
Even after I gave it the link to the mdn page it was still very suspicious and didnt give me a "you're absolutely right"
'using` isn't stage 4 yet.
If it gets conditional advancement at the plenary in 1 weeks time then it might make it in before ES2026 🤞🏻
github.com/tc39/agendas...
I don't immediately hate that code either.
I would love to start seeing more code unattach their abort handler when they complete - it's way too uncommon today.
Slide 9 isn't using 'using` on the DisposableStack btw
Looks like creating method stubs is a leak until restore is called.
Maybe worth calling out in the README @43081j.com?
"See this stash, don't try this again - you will lose marks"
Is this the one you're implementing in prolog?
Hey! I've got this stream queued up to watch next. Looks like it covers stores, nested getters, and diffing.
www.youtube.com/live/jfZdl3Q...
Thanks for the extra info Jovi!
I was reading the signals docs and was a little confused by preactjs.com/guide/v10/si...
The example shows passing in global signal, but looking at the implementation it looks like that would return Signal<Signal>.
I'm wondering if I'm missing something or if the docs are not the best example
Thanks Ryan! Much appreciated. I'll have a dig back though the old streams around that time.
@ryansolid.bsky.social was there a stream where you covered the solid 2.0 createStore ideas?
You talked about it briefly in the more recent stream and it sounded very interesting - only diffing store changes when there is a known listener (I think thats what I heard).
Thanks!
