Brandon McConnell

shiki.styleShikiA beautiful yet powerful syntax highlighter

13 Apr

@antfu.me is there an officially recommended way to support dedent-like functionality in shiki.style? hoping to add built-in dedent for code blocks without overriding shiki

10 Oct 2025

@adelfaure.bsky.social can i hire u for a new ascii project??

3 Sept 2025

@t0nyyates.bsky.social can i be added to your list? would love for people to be able to find me on x that way

1 Aug 2025

@jamie.build Hi Jamie, I'm updating an app to Tailwind 4 and noticing with some of my dialog exit animations that the dialog briefly reappears after animating out. This only happens intermittently. Any chance you'd be willing to take a look at this with me?

1 Aug 2025

I'm happy to open an issue for this as well, except there's a fair chance I'm just doing something wrong. 😅 I really appreciate you maintaining such a great plugin. I know a lot of work goes into that. I'm happy to compensate you for any time spent on this if you like.

19 June 2025

@miriam.codes I was curious if you knew of any spec work being done on CSS nesting support inside of @keyframes, so we can do things like this: @keyframes { 0% { width: 0px; > span { opacity: 0%; } } 100% { width: 50px; > span { opacity: 100%; } } }

17 June 2025

@chance.dev I'm curious how you'd approach this pattern if you were trying to strip out this useEffect. gist.github.com/brandonmccon... If a user is logged in, the root should redirect them to `/dashboard`. Otherwise, it redirects them to `/home`.

@danabra.mov the conversation is happening on X, but I was hoping you could clear something up for me? We’re having a discussion about Rules of Hooks, specifically using hooks inside of a render prop so the hooks are contained in the same render cycle, not passed between components

View full thread

x.comJoe Savona on X: "@branmcconnell It's great to see experimentation in this space and I'm super hesitant to chime in and ruin the parade. But just a heads up that this does break the Rules of Hooks since it's passing hooks as first-class values, so code using this library won't get compiled by React Compiler." / X@branmcconnell It's great to see experimentation in this space and I'm super hesitant to chime in and ruin the parade. But just a heads up that this does break the Rules of Hooks since it's passing hooks as first-class values, so code using this library won't get compiled by React Compiler.

Here is the most relevant message from Joe Savona over there: x.com/en_js/status... The conversation has progressed past that point into a few tangential conversations and DMs, but I think addressing and discussing the concern there would be fitting, both for my package and that article I shared^

And if you would rather not discuss it on X, I’m happy to continue that conversation right here in this thread on Bluesky TY 🙏🏼

unsplash.comCalling React Hooks Conditionally/Dynamically Using Render PropsIf you've used hooks at all, you'll know that one limitation is not being able to conditionally call them in the render body of your component. So what can we do if we really need to call a hook condi...

There’s one engineer from Meta, who chimed in, convinced that this violates Rules of Hooks, but based on my understanding of the documentation, I don’t think it should. This article’s implantation is nearly identical and makes the same non-violation claim: unsplash.com/blog/calling...

github.comSvelte 5: How to debug effect_update_depth_exceeded in a Svelte 4 library? · Issue #13192 · sveltejs/svelteDescribe the bug My team developed an extensive graphing library in Svelte 4. However, when trying to use the library in a Svelte 5 app, half of the features don't work and the error effect_update_...

13 May 2025

@paolo.ricciuti.me I saw you commenting on github.com/sveltejs/sve... and I'm having a similar issue. I'm wondering if you've learned anything new since that issue was resolved? I have a Svelte 5 app running with Svelte 4 syntax using the built-in compatibility mode.

13 May 2025

However, there is one specific part of my app where, every time that component renders, it throws the same error. None of these errors occurred when running Svelte 4, as this is a core part of our app, and upgrading to Svelte 5 following the Svelte 5 migration guide immediately caused this error.

13 May 2025

For context, I am not using `$effect` anywhere on in my app. Turning off my excluded directories when searching my codebase, the only places `$effect` appears are in root.svelte, the file svelte generates at `[ROOT]/.svelte-kit/generated/root.svelte`

30 Apr 2025

@miriam.codes I just released a new Tailwind plugin that adds support for the CSS Anchor Positioning API. I've had a few people ask me about polyfill support, and it looks like you maintain the leading polyfill.