It has all the same SSR APIs as React. The Octane website is rendered with Octane and the source is in the GitHub repository if you’re interested to see how it works

We just run a script that runs the benchmarks and updates the chart. It’s rounds numbers too. We’ve been as honest as possible in all the benchmarks - there’s no point in lying about a metric.

It's a relatively new domain, so corporate DNS servers are likely to block it.

There is definitely a bug there, I'll put up a fix in a bit. Thanks! :)

I contributed to React and Svelte on their core teams for years. Sometimes you just need to break free

Please can you create a Github issue with the security holes you've found? That would be greatly appreciated. I've given it a sweep and found nothing.

Sibling's proposed approach is a recipe for false positives.

Consider Claude Code's new /security-review prompt or just use the prompt starting from "Objective" after giving the context (see the Git shell commands) to Claude Opus 4.1.

https://raw.githubusercontent.com/anthropics/claude-code-sec...

Definitely Opus 4.1 though, not lesser.

I suggest do both.

Make a minimal zip of the the source code only (cut out anything not source code) drop it into ChatGPT and say "analyse this code for security flaws".

Then ask it for more.

Then do the same this with Google AI studio - drop the zipfile in and ask it to analyse for security flaws.

If you already did so why not share the answers you got?

I left Vercel a few weeks ago and I left the Svelte team earlier this year.

Thank you for all your contributions! Svelte 5 is a blast.

If you don't mind me asking, why did you leave? What do you plan on working on going forward?

It was a good time for change, I was working on Svelte 5 non-stop for two years! I'll be announcing my new role nearer the time :)

Makes sense xD

Best of luck! I'm curious to see what you come up with next.

I work on Svelte 5 and I was also a React engineer on the core team previously FWIW.

You can set the direction of the ElementNode explicitly to define LTR/RTL semantics. By default it’s automatically detected.

Thank you. I see. I guess I'm talking about the playground whereas I guess you're talking about Lexical itself and its API. It would be really nice to have a demo of this working with the API in the playground.

Thank for the detailed input. Would it be possible for you to create a GitHub issue around these (or many issues?) so that the team can track them and fix them. Thanks again!

Sorry, I’m just passing by and don’t want to interact further (I have no vested interest in the space at this time); up to you what you do with it.