> As of today, Turbopack can be used in Next.js v13. In the future we will be releasing a standalone CLI, plugin API, and support for other frameworks such as Svelte and Vue.

It is not ready for general usage for the moment, and it is still in alpha stage that isn't production ready and missing some crucial function such as PostCSS support. Nonetheless it is still exciting to see all the new innovation and healthy competition around JS bundler ecosystem.

Correct, still very early. While the happy path right now is through Next.js, there's a hacky workaround for general use outside Next.js. As we move forward in stability, we'll be publishing more guidance for using it as a general bundler with any framework. Next.js is helping dogfood Turbopack prior to that, while in alpha.

So then calling it a release is misleading. I don't mind it being called a component or module of Next.js in the meantime, but release makes it seem like it is standalone.

Just a simple inspect element can tell you that it use css "transform: rotate(-180deg)" on a up arrow. Don't be so harsh about this.

That was definitely my intent, but I'll add a little note in case it was too coy.

It is built on Forem: https://www.forem.com/

Open source here: https://github.com/forem/selfhost

Well the game can be beaten constantly with just 2 move...

Probably can impress your non-programmer friends?

> Probably can impress your non-programmer friends?

I'd say that's an accurate reason as to why this was also created... But yeah, not to hard to beat in just two turns!

You should be prepare to bear the consequence before you do something controversial, or you don't do it at the first place, simple as that.

More like angry gamers is enough with the greedy gaming companies that just want to add more cash grab while shipping out incomplete products.

Did you mean: preact

Preact uses a virtual DOM still.

Oh my bad, totally mess this up.

But I think VDOM is pretty much the core idea of react so it just wouldn't make sense for them to get rid of it. And also with React 18 coming with features like automatic batched updates and suspense, I would imagine it would be pretty hard to do without VDOM maybe?

may be it's one of challenges for devs, who ever are interested to make React alternative with same API and dev experiance without VirtualDOM support.

I don't think it is hacked, but erased by the author deliberately.