What languages and frameworks can I use in LiveCodes?

LiveCodes is a browser-based code playground, and its core promise is that it "just works" without a build step or local setup. That means the languages and frameworks you can use are the ones that run in a browser or can be compiled/transpiled client-side. The site itself loads as a JavaScript application (the page shows "Loading LiveCodes... Please enable JavaScript to use LiveCodes"), so JavaScript must be enabled in your browser before anything runs.

Because the public page evidence available here is limited to that loading message, the exact supported list should be confirmed inside the app. The sections below explain what a playground of this type typically covers, how to verify support yourself, and what to check before relying on it.

The baseline: web languages

Any code playground starts with the three languages of the web:

• HTML — page structure
• CSS — styling
• JavaScript — behavior

These are the safest assumption. If you only need to prototype a layout, test a CSS rule, or try a JavaScript snippet, LiveCodes is built for exactly that.

Beyond the basics: preprocessors and transpiled languages

Playgrounds in this category usually extend past plain HTML/CSS/JS by compiling other languages in the browser. Common examples include:

These work because the playground ships a compiler that runs client-side. The trade-off is startup time and bundle size — heavier languages load more slowly.

Frameworks and libraries

Front-end frameworks are usually supported through a starter template or by importing from a CDN. Likely candidates:

• React, Vue, Svelte, Preact, Angular, Lit
• Utility libraries such as jQuery, Tailwind CSS, Bootstrap

The practical question is not "is it listed?" but "can I import it?" If the playground allows arbitrary <script> or ES module imports from a CDN, you can pull in almost any browser-compatible library yourself.

How to check what's actually supported

Since the exact list isn't visible from the page evidence here, verify it directly:

1. Open LiveCodes in a browser with JavaScript enabled.
2. Look for a language or template selector — this is the authoritative list.
3. Pick a language and confirm it compiles and runs.
4. For a framework, start from its template if one exists; otherwise add a CDN import and test a minimal component.
5. Check whether the result renders in a preview pane and whether console output is visible.

Expected result: the selected language compiles without errors and the preview updates. If a language isn't offered, it either isn't bundled or must be added manually via CDN.

Common sticking points

• JavaScript disabled — nothing loads at all; the app is client-side only.
• CDN dependency — libraries imported from a CDN need network access and can break if a URL changes.
• Compile time — heavier transpiled languages feel slower on first load.
• Browser-only limits — server-side languages (Node.js backends, Python, databases) generally aren't available unless the playground explicitly emulates them in the browser.

What to decide

If your goal is quick HTML/CSS/JS prototyping or trying a front-end framework with zero setup, LiveCodes is a reasonable fit — just confirm your specific language or framework in the selector first. If you need server-side execution, a real build pipeline, or npm-based tooling, a local environment will serve you better.