Nmn
@nmn.sh
Intrigued if it can help me work on @stylexjs.bsky.social while spending less time.
February 4, 2026 at 10:21 PM
Intrigued if it can help me work on @stylexjs.bsky.social while spending less time.
The TLDR is that setState in React is usually asynchronous. So you need some kind of hook to detect when React is done applying the changes.
The slightly longer issue is that with Suspense and Transitions, you sometimes want to wait for async operations.
Doing all this in userland is very tricky.
The slightly longer issue is that with Suspense and Transitions, you sometimes want to wait for async operations.
Doing all this in userland is very tricky.
February 4, 2026 at 7:48 PM
The TLDR is that setState in React is usually asynchronous. So you need some kind of hook to detect when React is done applying the changes.
The slightly longer issue is that with Suspense and Transitions, you sometimes want to wait for async operations.
Doing all this in userland is very tricky.
The slightly longer issue is that with Suspense and Transitions, you sometimes want to wait for async operations.
Doing all this in userland is very tricky.
I think trying to advertise changing the handle to their domain as something desirable.
“Move from yourhandle.bsky.social to yourhandle.eurosky.social !!!”
I don’t know why someone would want to, but that seems to be what they’re selling.
“Move from yourhandle.bsky.social to yourhandle.eurosky.social !!!”
I don’t know why someone would want to, but that seems to be what they’re selling.
February 4, 2026 at 7:34 PM
I think trying to advertise changing the handle to their domain as something desirable.
“Move from yourhandle.bsky.social to yourhandle.eurosky.social !!!”
I don’t know why someone would want to, but that seems to be what they’re selling.
“Move from yourhandle.bsky.social to yourhandle.eurosky.social !!!”
I don’t know why someone would want to, but that seems to be what they’re selling.
@chriscoyier.net I would have be happy to chat and explain why view transitions don’t work reliably without using the component.
You make things work slightly better by waiting for a layoutEffect (and resolving a promise) but even that has its limits.
You make things work slightly better by waiting for a layoutEffect (and resolving a promise) but even that has its limits.
February 4, 2026 at 7:18 PM
@chriscoyier.net I would have be happy to chat and explain why view transitions don’t work reliably without using the component.
You make things work slightly better by waiting for a layoutEffect (and resolving a promise) but even that has its limits.
You make things work slightly better by waiting for a layoutEffect (and resolving a promise) but even that has its limits.
Yeah that might work.
<style id=“all-css”>
@import atomic from “/global.css”;
</style>
<template>
<style>
@import “#all-css”;
</style>
</template>
Do we even need @sheet for this if I just want all the same CSS? All we need is the ability to @import an ID.
<style id=“all-css”>
@import atomic from “/global.css”;
</style>
<template>
<style>
@import “#all-css”;
</style>
</template>
Do we even need @sheet for this if I just want all the same CSS? All we need is the ability to @import an ID.
February 2, 2026 at 8:40 PM
Yeah that might work.
<style id=“all-css”>
@import atomic from “/global.css”;
</style>
<template>
<style>
@import “#all-css”;
</style>
</template>
Do we even need @sheet for this if I just want all the same CSS? All we need is the ability to @import an ID.
<style id=“all-css”>
@import atomic from “/global.css”;
</style>
<template>
<style>
@import “#all-css”;
</style>
</template>
Do we even need @sheet for this if I just want all the same CSS? All we need is the ability to @import an ID.
If there was a way to import all css from root, maybe that would work.
Or if the ID could be used to importing where the id is on a link tag itself.
Or if the ID could be used to importing where the id is on a link tag itself.
February 2, 2026 at 5:41 PM
If there was a way to import all css from root, maybe that would work.
Or if the ID could be used to importing where the id is on a link tag itself.
Or if the ID could be used to importing where the id is on a link tag itself.
I don’t think @sheet helps with my gripes.
One issue is that bundlers like Vite will add a hash to the name of the css file and update the <link> tag in the HTML file but not in the various shadow doms which may even be rendered dynamically.
@sheet is cool for other use-cases, sure.
One issue is that bundlers like Vite will add a hash to the name of the css file and update the <link> tag in the HTML file but not in the various shadow doms which may even be rendered dynamically.
@sheet is cool for other use-cases, sure.
February 2, 2026 at 5:41 PM
I don’t think @sheet helps with my gripes.
One issue is that bundlers like Vite will add a hash to the name of the css file and update the <link> tag in the HTML file but not in the various shadow doms which may even be rendered dynamically.
@sheet is cool for other use-cases, sure.
One issue is that bundlers like Vite will add a hash to the name of the css file and update the <link> tag in the HTML file but not in the various shadow doms which may even be rendered dynamically.
@sheet is cool for other use-cases, sure.
I wrote about what I think is wrong or missing with the web component APIs.
There’s probably many more nice-to-haves that could be added, but I wanted to focus on what feels like the most obvious issues.
nmn.sh/blog/2026-02...
There’s probably many more nice-to-haves that could be added, but I wanted to focus on what feels like the most obvious issues.
nmn.sh/blog/2026-02...
February 2, 2026 at 5:05 AM
I wrote about what I think is wrong or missing with the web component APIs.
There’s probably many more nice-to-haves that could be added, but I wanted to focus on what feels like the most obvious issues.
nmn.sh/blog/2026-02...
There’s probably many more nice-to-haves that could be added, but I wanted to focus on what feels like the most obvious issues.
nmn.sh/blog/2026-02...
February 2, 2026 at 5:04 AM