WeSearch

OXP – Write one WASM extension, run natively in VS Code, JetBrains, and Neovim

OXP Protocol· ·2 min read · 0 reactions · 0 comments · 13 views
#technology#software#development#programming
OXP – Write one WASM extension, run natively in VS Code, JetBrains, and Neovim
⚡ TL;DR · AI summary

The OXP runtime v0.1 has been released, allowing developers to create a single extension that runs natively across multiple IDEs, including VS Code, JetBrains, and Neovim. This new approach promises true portability with a universal API surface, eliminating the need for compromises or extensive tweaks. The OXP framework utilizes modern tools and offers features like sandboxed micro-frontends and native rendering.

Key facts
Original article
OXP · OXP Protocol
Read full at OXP →
Opening excerpt (first ~120 words) tap to expand

Runtime v0.1 shipped · VS Code · JetBrains · NeovimBuild one extension. Run across every IDE.VS Code · JetBrains · Neovim · Cursor · Windsurf — write it once, ship it everywhere on the open OXP runtime.KSearchPopular:reactpythonthemesgitaijupyter2,514MCP Servers5Compatible IDEsOpenProtocolBuilt inEuropeVS CodeVS CodeCursorCursorWindsurfWindsurfJetBrainsJetBrainsNeovimNeovimVS CodeVS CodeCursorCursorWindsurfWindsurfJetBrainsJetBrainsNeovimNeovimShipping nextv0.1 is live. v0.2 is already in flight.Specified in WIT. Implemented on all three hosts. Rolling out as soon as conformance tests go green — no waiting on a 2027 milestone.Native UI surfacesui/render painted into real tool windows on JetBrains and floating windows on Neovim.

Excerpt limited to ~120 words for fair-use compliance. The full article is at OXP.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from OXP