@thdxr@redshiftpress@thdxr does that mean the single session owns the config? How do you kill it so it reloads the config. Had this issue with Claude agents which I am guessing may be a similar config. Can we have reload config option π
@matteocollina@nodejs@bunjavascript I did, but when 26 came out I didnβt see a new build so wasnβt sure if it was just a one off build for your post.
@platformatic Do you see the Node team providing offical docker hub builds with this features enabled? I tried the image and can definitely see the memory reduction.
@matteocollina read, your recent article about pointer compression. Is Node planning to provide offical builds with pointer compression turned on? I switched the image on dev and can see significant savings in memory. Would love to use this in production.
@paper hey awesome team. Any way to share designs in a readonly way. I have pro and can only add editors and administrators.
Need to collaborate with stakeholders and designers who currently are using Figma.
I canβt figure out how to export to an image. Is that possible?
@Jean__Meche@stephenlautier Can you show me an example of where this is done? When we wrap a signal with Form. We have two CVA components and two inputs. The signal updates the two inputs but does not see the CVA components. Atleast this was the case in v21
@stephenlautier@Jean__Meche Custom built components implementing CVA do not work with [field]. We thought that signal forms could detect a CVA component was being bound and would build some sort of internal adapter. Something similar to the GitHub link but automatically done internally by the Field
@opencode is anyone else experiencing massive token usage on Claude Opus like getting to 100k in just a few prompts. Previously we could plan and execute in a single session.