Today is my last day at @the-guild.dev! I still intend to continue my work on projects like polen.js.org, and graffle.js.org. I've been head down for a few months culminating to my talks at @graphql.org Amsterdam conference two weeks ago. Feel a bit burnt out but also excited for new adventures.

@hiogawa.bsky.social‬ thanks for your work on Vite RSC, using it this week on a framework we're building at @the-guild.dev! I ran into one issue with RR which is that our routes.ts module has virtual imports. I adjusted your rr plugin code to use environment module runner import instead ...

I am thrilled (and nervous 😬) to have been selected as a speaker to share work we’re doing at @the-guild.dev on GraphQL API documentation. It’s still super early but being worked on in open at github.com/the-guild-or....

I pushed my knowledge/muscle-memory on Vite Dev/NodeJS Package SubPaths/Tree Shaking/Isomorphic FS/Path/... github.com/the-guild-or...

Hello github.com/jasonkuhrt/kit Over the past weeks I have been passively factoring out utilities I use across my projects. For now my niche thing and changing constantly, but I am creating it as a proper library. It has hints of @effect-ts.bsky.social mixed with es-toolkit/ramda/fs-jetpack/...

I want to make a @zed.dev extension that leverages @typescriptlang.org semantic analysis allow syntax theme authors (including would be me :)) to apply rules 🧑‍🎨 also on arbitrary static analysis ala. what @typescript-eslint.io is doing for listing. Leverage TS Go to make it perform.

@ieni.dev! Please bring Glimpse ( marketplace.visualstudio.com/items?itemNa...) to @zed.dev! ❤️ This time you'd get to write it in 🦀😄. I think it would integrate really nicely with Vim concept of key chords since they do exactly that: <key><...key> -> do something 🚀.

This is going to be great, we can finally steer people away from using POST by "default" (PO's require effort et all) on GraphQL because QUERY is an ideal replacement 😍

I'm so happy @zed.dev exists. Finally made the switch yesterday. Never going back to VSCode. Thanks for the great last ~7 years. But it became too buggy and slow for me on an hourly basis. 🤷 (being a vim user definitely made me hit more rough edges than otherwise would have).

Went down a rabbit hole on TS "... cannot be named ..." error. There appears to be a bug in TS with ESM re-exports and namespaces, but I'm not sure! Tricky whatever it is. I've tried to document the issue clearly here (+solution): github.com/jasonkuhrt/r.... TS issue here: github.com/microsoft/Ty...

I submitted two talks for this year. One for Graffle and one for a new project I recently started at @the-guild.dev. More to share about the latter in the coming weeks :))

Hey @vlt.sh @ruyadorno.com I am looking for a library that not only reads package.json but also normalizes it (e.g. bin is string or record, but normalized should just be record). Does any of your libraries do that?

🙇‍♂️ Thank you @vlt.sh @ruyadorno.com et al. for giving the community a cohesive toolkit for working with packages docs.vlt.sh/packages. I wish I had some of these when I was building Paka with @schickling.dev ❤️!

I didn't not expect that building the devtools messaging protocol for @livestore.dev would turn out to be one of the most difficult parts to build. In order to support reliable and efficient messaging (supporting transferables), I ended up building a local networking protocol called "Webmesh".

I finally clawed myself out of a self-inflicted rabbit hole. I will not be doing "that" again (multi-month PRs). Graffle is in a better place at core with a brewing reactive config system but there are many fast follows left to do. Happy to be back on track again! github.com/graffle-js/g...

If you need a sublet this summer in Montreal my home is available! It's dear to me and excited to host someone. :) montreal.craigslist.org/sub/78435679...

I have been working hard this year to bring clarity to my life. A part of that involves reviewing implicit contracts I've had with myself about workaholism. I love working on open source libraries but it cannot anymore come at the expense of my own life. So for example, today (Sunday) I am ...

This is another great example of how well @cloudflare.social is playing with the open source ecosystem: not a simple use case report but a full-fledged and generic new API proposal for @vite.dev. More companies should have dedicated teams actively working with open source projects like they do.

Recent improvements to my TypeScript library template. Many dependencies updated and a lot of streamlining around ESLint github.com/jasonkuhrt/t....

A glimpse at what’s coming to Effect Days: ◆ AI Agents ◆ Error Management & Testing ◆ Effect Cluster & Fibers ◆ Next-Gen DevTools ◆ Rebuilding Redis for great Effect ...and much more! 🎟️ Get your ticket now: effect.website/events/effec...

Just dropped one of my seasonal updates on Graffle! Winter this time ☃️ github.com/graffle-js/g....

GraphQLConf 2025 CFP is now open. Submit your talk ideas by May 4!

Hey, fellow Canadians 🇨🇦, these links might be useful for us for the foreseeable future: - madeincanadadirectory.ca - madeinca.ca Send it around :)

We just released the beta for TypeScript 5.8! This release brings support for Node.js' require(ESM), smarter/safer checks for functions using advanced types, a few great optimizations for editor scenarios, and more. Give it a try! devblogs.microsoft.com/typescript/a...

TypeScript 5.8 seems to be adding something interesting for library developers that think about using "Simplify" type utilities to make their interface types with complex type calculations readable: github.com/microsoft/Ty....

Self-soothing on a quiet Sunday morning 😅. This (impulsive large rewrites) is something that typically does not fly in organizational team contexts. However, in my work, it does happen periodically. The ability to pursue ideas unbounded is both a blessing and a curse. github.com/graffle-js/g...

Just write a barebones guide for Performance tips with @shiki.style. If you use Shiki in your project, check it out and help us improve the guide! 🙌 shiki.style/guide/best-p...

That's where @effect-ts.bsky.social shines. I'm using it for this particular use case extensively in various projects where the same code is used across web/node/service workers. Even natively supports transferable objects (i.e. moving memory instead of copying). Here is an example schema:

HTTP Headers data in the JS ecosystem feels a mess to me. (1) Inconsistent usage, e.g. this today github.com/graphql/grap.... (2) No merge methods, just set/append. I wonder how many subtle bugs hit production via nth hand rolls out there. Do you have a better story here @effect-ts.bsky.social?

I find written communication for collaboration difficult, expending significant energy to output considered concise clear prose. I usually lack such energy. My odd revisit to past messages typically feels disappointing. I started playing with Apple Intelligence writing tools today. It helps 🙂.

From the beginning of @graphql.org I appreciated its inclusion of a specification. If you're like me in that regard, and wonder if there is still interesting iteration happening on specs there, the answer is yes. Here's one I'm excited to learn more about github.com/graphql/comp....

The clincher TL;DR: > The EPOCH version is for those big announcements, while MAJOR is for technical incompatible API changes that might not be significant. In theory: yes * ♾️ ❤️ 🙏 In practice: Feels like a huge ecosystem lift, but worth it.

Wondering about parameterized fixtures for Vitest 🤔 github.com/vitest-dev/v...

If you're going to produce a physical book in 2024, produce something beautiful. This is great. Sold. ❤️

Happy new year from Montreal 🇨🇦

Dotan was experimenting with this library to have a TS parser for GraphQL: github.com/dotansimha/g.... I’m curious about the Document side parsing for clients. The parser is not so hard, but I’m concerned about performance. DX potential here is high. @jovidecroock.com thoughts?

The tooling has become quite good but I find frustration in needing to piece multiple packages together to achieve type safety. I don’t want to use a lsp or file watcher to generate types. Give me a shakeable client I can generate once and use. Ala Genql or Graphql-Zeus but more mainstream.

I love to hear how authors contributing their talents to open source have their lives changed in the process. Nice that it’s not only burnout. Stay vigilant though :)

Have you or are you using a GraphQL client? If so what were/are the friction points? Either direct client issues or tangential GraphQL/stack issues. Would love to know!

Graffle's document builder is now realized as an extension graffle.js.org/extensions/d... as of today github.com/graffle-js/g.... Thus, a bare Graffle client is now 17kb compressed. This resolves the months long work of reducing bundle size github.com/graffle-js/g.... Up next is improved docs.

I was working towards such a list myself, glad to see others were too!

The work to optimize Graffle's bundle size is paying off and it's going to get smaller. Document builder will become an extension, big win if not using. I can refactor some other areas too. @jovidecroock.com I want to look into if graphql.web can be smaller. Its pointing at a dist though...

github.com/graffle-js/g... User gratitude goes further than you might think. Thanks Lesha ❤️.

🤣 +1

Just discovered Relative CI while working on Graffle bundle size check automation. relative-ci.com. Definitely going to be looking more closely at this! <3

Just added an example for Graffle showing off the selection set types it gives. For users this is not interesting until it's suddenly essential 😊 (for their own type-safe abstractions). graffle.js.org/examples/typ.... I'm excited for feedback on ways to make even better utility types.

🚀 Big News: GraphQLConf is coming to Amsterdam this Fall 🎉 Join us for 3 days of networking & deep dives into all things #GraphQL 📅 Date: Sept. 8-10, 2025 📍 Location: Pakhuis de Zwijger 🌟 Read the Blog: graphql.org/blog/announc... 👨🏽‍💻 graphql.org/conf/2025/ #GraphQLConf

Building with Effect and EdgeDB: Part 1 By Aleksandra Sikora www.edgedb.com/blog/buildin...

When you have to do some imperative programming for whatever reason #TypeScript flow analysis is pretty awesome. Here's an example I hit today that reminded me of that 😊.

New example showing off how Graffle's bare preset gives you the library at its most minimal. When there is no transport, request methods statically adjust to help you understand this missing requirement. And if you dislike it, you can opt-out with a one-liner config. graffle.js.org/examples/pre...