ꪖꪶꫀᥴ ꪶꪖ᥅ᦓꪮꪀ
@retropragma.bsky.social
got a sick new logo for my RPC library, alien-rpc :)
July 14, 2025 at 6:26 PM
got a sick new logo for my RPC library, alien-rpc :)
damn, i thought that unjs was gonna pull through for me on this one
May 8, 2025 at 3:27 PM
damn, i thought that unjs was gonna pull through for me on this one
so... what npm library do you use for reading config files?
May 8, 2025 at 3:22 PM
so... what npm library do you use for reading config files?
May 6, 2025 at 12:59 AM
lmao, thanks github
April 23, 2025 at 6:50 PM
lmao, thanks github
"This results in much smaller and faster output"
Not a fan of hand-wavy claims like this, even if true. The name mangling is such a horrid DX when debugging that I'm not sure it's worth the proclaimed benefits.
Not a fan of hand-wavy claims like this, even if true. The name mangling is such a horrid DX when debugging that I'm not sure it's worth the proclaimed benefits.
March 25, 2025 at 4:31 PM
"This results in much smaller and faster output"
Not a fan of hand-wavy claims like this, even if true. The name mangling is such a horrid DX when debugging that I'm not sure it's worth the proclaimed benefits.
Not a fan of hand-wavy claims like this, even if true. The name mangling is such a horrid DX when debugging that I'm not sure it's worth the proclaimed benefits.
just found out that object spreads are less strict than i'd expect.
www.typescriptlang.org/play/#code/G...
www.typescriptlang.org/play/#code/G...
March 21, 2025 at 3:10 PM
just found out that object spreads are less strict than i'd expect.
www.typescriptlang.org/play/#code/G...
www.typescriptlang.org/play/#code/G...
Neon has the most useless usage page
March 8, 2025 at 2:46 PM
Neon has the most useless usage page
i'm surprised that chatgpt got this one wrong
February 18, 2025 at 6:08 PM
i'm surprised that chatgpt got this one wrong
Oh and I forgot to mention that a RedisKey can be used as a singleton or as a namespace. Also useful for patterns.
February 13, 2025 at 9:37 PM
Oh and I forgot to mention that a RedisKey can be used as a singleton or as a namespace. Also useful for patterns.
Here's an example of using what I'm calling “modifiers” which are basically options for certain commands.
In this example, we are setting "foo" only if it doesn't already exist, then we're returning the previous value.
As you can see, the naming is aligned with Redis' naming.
In this example, we are setting "foo" only if it doesn't already exist, then we're returning the previous value.
As you can see, the naming is aligned with Redis' naming.
February 13, 2025 at 9:10 PM
Here's an example of using what I'm calling “modifiers” which are basically options for certain commands.
In this example, we are setting "foo" only if it doesn't already exist, then we're returning the previous value.
As you can see, the naming is aligned with Redis' naming.
In this example, we are setting "foo" only if it doesn't already exist, then we're returning the previous value.
As you can see, the naming is aligned with Redis' naming.
Hash maps are supported!
I'd like to support all Redis commands, but need someone with the time to put them in. It's not a difficult thing to do.
I'd like to support all Redis commands, but need someone with the time to put them in. It's not a difficult thing to do.
February 13, 2025 at 9:06 PM
Hash maps are supported!
I'd like to support all Redis commands, but need someone with the time to put them in. It's not a difficult thing to do.
I'd like to support all Redis commands, but need someone with the time to put them in. It's not a difficult thing to do.
February 13, 2025 at 8:59 PM
As I said, quite a bit lighter than ts-morph. 😄
February 3, 2025 at 12:23 AM
As I said, quite a bit lighter than ts-morph. 😄
lastly, array updates caused by native methods are coalesced into single events, making the logs more readable.
by default, valtio only has knowledge of index operations (set or delete) and native calls translate to them opaquely, so i had to inject some extra logic to track the native calls :)
by default, valtio only has knowledge of index operations (set or delete) and native calls translate to them opaquely, so i had to inject some extra logic to track the native calls :)
January 31, 2025 at 8:31 PM
lastly, array updates caused by native methods are coalesced into single events, making the logs more readable.
by default, valtio only has knowledge of index operations (set or delete) and native calls translate to them opaquely, so i had to inject some extra logic to track the native calls :)
by default, valtio only has knowledge of index operations (set or delete) and native calls translate to them opaquely, so i had to inject some extra logic to track the native calls :)
it even tags values with a unique, human-readable identifier so you know what they represent. you can assign your own identifier with setDebugId() if you want.
if a property starts with "#" that means it's a reactive variable inside your createClass() factory function
if a property starts with "#" that means it's a reactive variable inside your createClass() factory function
January 31, 2025 at 8:31 PM
it even tags values with a unique, human-readable identifier so you know what they represent. you can assign your own identifier with setDebugId() if you want.
if a property starts with "#" that means it's a reactive variable inside your createClass() factory function
if a property starts with "#" that means it's a reactive variable inside your createClass() factory function
valtio-kit's next version will inject debugging hooks into valtio so it can provide automatic logging for valtio state updates.
it has a powerful filtering mechanism, with opt-in console.trace() for specific values.
it has a powerful filtering mechanism, with opt-in console.trace() for specific values.
January 31, 2025 at 8:31 PM
valtio-kit's next version will inject debugging hooks into valtio so it can provide automatic logging for valtio state updates.
it has a powerful filtering mechanism, with opt-in console.trace() for specific values.
it has a powerful filtering mechanism, with opt-in console.trace() for specific values.
The cursed Parcel mangling rears its ugly head once again 😵
January 31, 2025 at 7:46 PM
The cursed Parcel mangling rears its ugly head once again 😵
oh no. who would publish to npm like this? 😔
January 21, 2025 at 10:55 PM
oh no. who would publish to npm like this? 😔
If you're curious, here's the compiled code.
January 10, 2025 at 9:44 PM
If you're curious, here's the compiled code.
3 new features being added to valtio-kit today:
• re-assigned parameters are reactive
• onUpdate lets you receive updated parameters from component rerenders
• property assignments can be reactively bound to a computed(…) expression
• re-assigned parameters are reactive
• onUpdate lets you receive updated parameters from component rerenders
• property assignments can be reactively bound to a computed(…) expression
January 10, 2025 at 9:41 PM
3 new features being added to valtio-kit today:
• re-assigned parameters are reactive
• onUpdate lets you receive updated parameters from component rerenders
• property assignments can be reactively bound to a computed(…) expression
• re-assigned parameters are reactive
• onUpdate lets you receive updated parameters from component rerenders
• property assignments can be reactively bound to a computed(…) expression
and here's what it gets compiled to:
January 8, 2025 at 7:40 PM
and here's what it gets compiled to:
a little sneak peek... this is a screenshot of an E2E test of the plugin's compiler and runtime :)
January 8, 2025 at 7:38 PM
a little sneak peek... this is a screenshot of an E2E test of the plugin's compiler and runtime :)
Added support for the "class" prop to my vite-react-classname plugin. It's transformed into "className" at compile time. It accepts an inline array expression. It's ✨automagically✨ forwarded in your function components.
January 6, 2025 at 4:53 PM
Added support for the "class" prop to my vite-react-classname plugin. It's transformed into "className" at compile time. It accepts an inline array expression. It's ✨automagically✨ forwarded in your function components.