Vue SFC Playground has nowhere to enable `createVaporApp`

[LoTwT]

Vue version

3.6.0-alpha.1

Link to minimal reproduction

https://play.vuejs.org/#eNp9Uc1KAzEQfpUxl1Wwu5aKh7ItqBTUg4oKXgKybKfb1GwS8rMWln13JymtPUhPyXw/k28mPbs1Ju8CsikrXW2F8eDQBwNdZbSdcyVaOj30YHEFA6ysbiEjQ8YVV7VWzkPrGphF/jx7QCk1fGorl2fZBVdlsWtKjajw2BpZeaQKoFyP532fzMNQFlQlVCgTPHSjVi9RzjgjnjMoiCyLIz+7ZN7R8yvR5BunFeXvo5+zWrdGSLQvxguKx9kUEhO5itL9PCXM24CXe7xeY/39D75x24hx9mrRoe2QswPnK9ug39GL92fc0v1AUvogSX2CfEOnZYgZd7K7oJYU+0iX0j6m/QvVfLjF1qNy+6Fi0Kgckp4z+pP7E6P/xZ3k18nH1UBb/OrQxp60wEl+k1+NKmnWVT5mwy/qSrFX

Steps to reproduce

• open a new Vue SFC Playground
• find nowhere to use the createVaporApp

What is expected?

should have somewhere to enable createVaporApp

What is actually happening?

have nowhere to use createVaporApp

System Info

Any additional comments?

No response

[Notmanik]

Hey! 👋

I looked into the Vapor Mode stuff you were exploring and here’s a quick summary of what I found:

You were right about using .vapor.vue filenames and <script setup vapor> — that's exactly how Vue identifies and compiles a component in Vapor Mode (as of Vue 3.6+).

The problem is that none of the online playgrounds (including play.vuejs.org and vapor-repl.netlify.app) fully support Vapor Mode right now. The setText error you're seeing is due to the CDN versions missing parts of the Vapor runtime (vue/vapor) and related compiler transforms.

Even the Vue Template Explorer doesn’t actually compile with Vapor — it just parses the code as normal <script setup> and doesn’t enable any real Vapor features.

I tested it locally by setting up a project with the latest vue-vapor-playground repo, and it worked perfectly there. So Vapor Mode is functional — just not in any online sandbox yet.

I'm still trying to find a way to make this more accessible or replicable online — I’ll hit you up as soon as I find something cleaner or easier to test. 🙌

[edison1105]

The Playground does not yet support pure createVaporApp. Currently, it uses createApp + vaporInteropPlugin, this means the root component (App.vue) cannot be a vapor component.
You can create a local project for testing, or do it like this

EDIT

• fixed via chore(sfc-playground): import vaporInteropPlugin only if Vapor mode is supported #13645
• It will auto use createVaporApp if App.vue is a vapor component

[Notmanik]

Ahh yeah I saw that too.

I tried exactly that approach — using createApp with the vaporInteropPlugin, and made sure App.vue was a normal component while importing a .vapor.vue child component.

But still ran into the same error:

The requested module 'vue/runtime-dom' doesn't provide an export named 'setText'

Even doing stuff like getCurrentInstance()?.vapor or getCurrentScope() doesn't help — it breaks as soon as any component tries to use Vapor-specific features like vue/vapor imports.

So yeah, doesn't seem like the playground can simulate Vapor properly even with interop mode. Only fully worked for me when I cloned the vue-vapor-playground repo and ran it locally.

Still hoping they add full support in the playground soon, but for now local setup seems to be the only reliable way.