Alex
@alexdln.com
Web Engineer, Author, Contributor, Photographer
Frontend/React/Next.js/UX/DX/Сapybara/Performance/Growth
🔨 Building slidebook.dev | atsky.app | robindoc.com | nimpl.dev
🏡 Living alexdln.medium.com | github.com/alexdln
Frontend/React/Next.js/UX/DX/Сapybara/Performance/Growth
🔨 Building slidebook.dev | atsky.app | robindoc.com | nimpl.dev
🏡 Living alexdln.medium.com | github.com/alexdln
Well, I can understand when it's just another startup, but @github.com, how?
November 11, 2025 at 6:24 PM
Well, I can understand when it's just another startup, but @github.com, how?
And this is the file that allows to control all such changes and guarantee the reliability of their typing
![// interface TestStore {
// count: number;
// name: string;
// user: {
// id: number;
// email: string;
// };
// theme?: "light" | "dark";
// items: string[];
// }
// Update should accept partial store
update({ count: 1 });
update({ name: "New", theme: undefined });
// @ts-expect-error - should not accept undefined value if it was not defined in the store
update({ name: "New", items: undefined });
update({ name: "New", items: [] });
update((prev) => ({ count: prev.count + 1 }));
// @ts-expect-error - should not accept invalid key
update({ invalidKey: "value" });
// @ts-expect-error - should not accept undefined value if it was not defined in the store
update((prev) => ({ count: prev.count + 1, items: undefined }));
update((prev) => ({ count: prev.count + 1, items: [] }));](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:er6erflnnxcozlbqmrpflt6h/bafkreiap5nshbt7pcy6nndmzajw7rpuvguqbog3rfmw4actbborxwfgesy@jpeg)
November 11, 2025 at 1:05 PM
And this is the file that allows to control all such changes and guarantee the reliability of their typing
These simple checks make updates and optimization much easier, and also provide strong protection against accidental generic breakage
![// Test 4: useStore with keys
function testUseStoreWithKeys() {
const data = useStore(Store, { keys: ["count", "name"] });
// Should return only selected keys
const count: number = data.count;
const name: string = data.name;
// @ts-expect-error - should not have unselected keys
const user = data.user;
// @ts-expect-error - should not accept invalid keys
const invalid = useStore(Store, { keys: ["invalidKey"] });
}
// Test 5: useStore with mutation
function testUseStoreWithMutation() {
// Mutation without keys
const doubled = useStore(Store, {
mutation: (Store) => Store.count * 2,
});
const doubledType: number = doubled;
// Mutation with keys
const computed = useStore(Store, {
keys: ["count", "name"],
mutation: (Store) => `${Store.name}: ${Store.count}`,
});
const computedType: string = computed;](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:er6erflnnxcozlbqmrpflt6h/bafkreiakgatmntxgls2deewdd4p6g6oy2xjsm63rhu64dnbmbi4e7mn6rq@jpeg)
November 11, 2025 at 10:22 AM
These simple checks make updates and optimization much easier, and also provide strong protection against accidental generic breakage
Just in case, I will translate it into another language so that more people can understand.
Broken scrollbars have become too common problem 🫠
This is what happens when the entire company is Apple-powered...
* Please don't use w-screen within a scrollbar element, use w-full *
Broken scrollbars have become too common problem 🫠
This is what happens when the entire company is Apple-powered...
* Please don't use w-screen within a scrollbar element, use w-full *
November 10, 2025 at 9:35 PM
Just in case, I will translate it into another language so that more people can understand.
Broken scrollbars have become too common problem 🫠
This is what happens when the entire company is Apple-powered...
* Please don't use w-screen within a scrollbar element, use w-full *
Broken scrollbars have become too common problem 🫠
This is what happens when the entire company is Apple-powered...
* Please don't use w-screen within a scrollbar element, use w-full *
By the way, I still can't decide for myself about portals - do I want to use them, or is it better to create a global store and communicate through it (with Contection it costs nothing)
November 10, 2025 at 4:04 PM
By the way, I still can't decide for myself about portals - do I want to use them, or is it better to create a global store and communicate through it (with Contection it costs nothing)
I’ve dreamed of being an engineer since childhood. I used to think it would be all about technical drawings and similar things (which I really loved), but programming has captivated me even more!
November 10, 2025 at 3:54 PM
I’ve dreamed of being an engineer since childhood. I used to think it would be all about technical drawings and similar things (which I really loved), but programming has captivated me even more!
Well, now it’s even more stable and reliable 🧑🔧
![[Success] Daily auto tests for React Canary
Daily auto tests for React Canary #3: Manually run by alexdln
main
2 minutes ago 29s
[Failed] Daily auto tests for React Canary
Daily auto tests for React Canary #2: Manually run by alexdln
main
11 minutes ago 25s
[Failed] Daily auto tests for React Canary
Daily auto tests for React Canary #1: Manually run by alexdln
main
20 minutes ago 28s](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:er6erflnnxcozlbqmrpflt6h/bafkreihlk7hux6s4x3acetdncxkakjhzvy2m5a5o5xi32lko3qd22dmisy@jpeg)
November 10, 2025 at 3:46 PM
Well, now it’s even more stable and reliable 🧑🔧
Canary channel testing is one of the important implementations that allows for the timely detection of breakages related to framework API changes. You immediately see what has changed and fix it.
This has saved @nimpl/getters several times with critical changes in next.js
This has saved @nimpl/getters several times with critical changes in next.js
November 9, 2025 at 10:22 PM
Canary channel testing is one of the important implementations that allows for the timely detection of breakages related to framework API changes. You immediately see what has changed and fix it.
This has saved @nimpl/getters several times with critical changes in next.js
This has saved @nimpl/getters several times with critical changes in next.js
All that's left is to set up automated tests on the canary channel and e2e tests for next.js (I don't know if other frameworks have enough specifics, I'll decide later)
November 9, 2025 at 10:13 PM
All that's left is to set up automated tests on the canary channel and e2e tests for next.js (I don't know if other frameworks have enough specifics, I'll decide later)
The magic in this example is that the re-rendering only occurs when the mutation result changes. This isn't just an optimal subscription to store changes, but a targeted optimization to a specific place
November 9, 2025 at 10:12 PM
The magic in this example is that the re-rendering only occurs when the mutation result changes. This isn't just an optimal subscription to store changes, but a targeted optimization to a specific place
Although in the case of markup or queries, translators won't be able to handle it, and the changes will create duplicates
Okay, that was a bad idea 😅
Okay, that was a bad idea 😅
November 9, 2025 at 10:08 PM
Although in the case of markup or queries, translators won't be able to handle it, and the changes will create duplicates
Okay, that was a bad idea 😅
Okay, that was a bad idea 😅