Open-source project
imba/imba avatar
imba/imba

Imba: a web language with tags and styles in the syntax, an esbuild-based imba command, and alpha tooling

🐤 The friendly full-stack language

6,514 stars184 forksJavaScriptMIT

At a glance

What is it?
imba/imba is the MIT-licensed home of Imba, a full-stack language that compiles to JavaScript and treats DOM nodes and CSS as language features. The language and its bundler are the draw; the alpha editor tooling and a GitHub releases page frozen in 2022 are the parts to check before committing.
Who is it for?
Imba fits developers who want markup, styling and logic in one terse syntax, are comfortable on Node and npm, and are willing to learn a new language for a smaller toolchain with a built-in esbuild bundler. It does not fit teams that need mature editor tooling today, since the TypeScript-plugin-based tooling is still alpha, or teams that track versions through GitHub releases, which stop at vite-plugin-imba 0.10.1 from 2022-10-24.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository received new commits within the last day.
What is it written in?
Mainly JavaScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • imba/imba6,514 ★ · +5
Star history
Repository2026-09-232026-11-15
imba/imba6.5k6.5k

5 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Tags are a language construct, not a library call

Imba compiles to JavaScript and has language-level support for defining, extending, subclassing, instantiating and rendering DOM nodes. A component is declared with tag, and it can extend a built-in element: the login example declares tag login-form < form, so the component is a form. Inside it, <self> refers to the element itself, event handlers attach with modifiers such as @submit.prevent, and form fields bind to variables with bind=name and bind=secret. Text interpolation uses braces, as in "Login as {name}". The example ends with imba.mount, which renders the tag into the page with inline layout styles applied in square brackets. On the front end, Imba is positioned as a replacement for Vue or React rather than a layer on top of them.

Styles live in the tag tree with Tailwind-style shorthands

Imba takes its styling model from Tailwind and moves it into the language. A global css block styles an element everywhere, a css line inside a tag scopes the rule to that component, and square brackets on an element apply inline styles. Rules can also be scoped to a file or to part of a tag tree. Properties accept long names such as position: relative and background, or shorthands such as pos:relative, d:block and bg:blue5. Modifiers attach state and media conditions to a single property: @hover, @lg, @landscape and @dark. The example bg@hover:blue6 changes the background only on hover. The cost is that these shorthands are Imba's own vocabulary, so a team reading Imba code has to learn them alongside the language.

The imba command bundles with esbuild and drops the dev and prod split

Imba ships a built-in bundler based on esbuild. Running an app with the imba command bundles and compiles Imba code together with TypeScript, CSS and other file types, and reloads both server and client automatically. Imports cover stylesheets, images, TypeScript, HTML and workers without configuration:

imba
# importing a worker
const worker = import.worker './analyzer'
const analyzer = new Worker(worker.url)
# import an image
const logo = import './images/logo.png'
console.log "logo size: {logo.width}x{logo.height} - at {logo.url}"

An imported image exposes width, height and url, and import.worker returns an object whose url feeds a Worker. Bundling happens on demand, and the project states there is no difference between production and development mode.

One language for Express routes and the browser

Imba runs on the server as well as the client and works with the Node ecosystem, including npm packages. The server example imports express, a TypeScript module, an HTML file and a PNG, then defines routes with app.get and a do block. One route builds a response with String <html> <body>, rendering Imba tags to an HTML string on the server; another returns the imported HTML file's body. The project cites Scrimba.com, its learning platform with 100K+ monthly active users, as running Imba on both its front end and back end. That is the main production reference offered, and it comes from the language's own authors.

Type annotations depend on a TypeScript server plugin that is still alpha

Imba's editor support is implemented as a TypeScript server plugin. It provides intellisense, diagnostics and cross-file refactorings that also work with .js and .ts files in the same project. Code can import types the way TypeScript does, as in import type { CookieOptions } from 'express-serve-static-core', and annotate variables and parameters with a backslash, as in res\Response and options\CookieOptions.

The project itself says the tooling is still in alpha, like the language. For a team, that means editor diagnostics and refactors can be wrong or missing, and type checking is not a safety net you can lean on in review. Plan for that before porting a codebase that relies on TypeScript's checks today.

GitHub releases stopped at vite-plugin-imba 0.10.1 in 2022

The repository's GitHub releases do not track the language. The three most recent entries are all for vite-plugin-imba: 0.9.1 on 2022-10-13, 0.10.0 on 2022-10-19 and 0.10.1 on 2022-10-24. Meanwhile the repository's last push was on 2026-11-02, so work continues without matching GitHub releases.

The consequence is that the releases page is not where you find the current Imba version or its changes. The package is published on npm as imba, and that listing is the place to check versions. Anyone pinning versions by watching GitHub releases will see nothing new.

The monorepo root is tooling, published with Lerna

The root package.json is a private package named imba-monorepo. Its declared workspaces are five tooling packages: imba-language-core, imba-language-server, imba-typescript-plugin, vscode-imba-next and create-imba. Development uses TypeScript ^5.8.0, Vitest ^3.0.0 and @types/node ^22.0.0.

Publishing goes through Lerna. The release script runs lerna publish, and the prereleasez script publishes canary builds with a preid built from the last commit timestamp under the next dist-tag on npm. The deploy-site script opens an SSH session to [email protected], so it is an operations script for maintainers, not something a contributor can run. The README's own getting started path is the browser playground at imba.io/try and the official guide at imba.io, with questions handled on Discord.

Editorial conclusion

Imba fits developers who want markup, styling and logic in one terse syntax, are comfortable on Node and npm, and are willing to learn a new language for a smaller toolchain with a built-in esbuild bundler. It does not fit teams that need mature editor tooling today, since the TypeScript-plugin-based tooling is still alpha, or teams that track versions through GitHub releases, which stop at vite-plugin-imba 0.10.1 from 2022-10-24. Before adopting it, try your patterns in the playground, read the guide at imba.io, and check npm for the current imba version since the repository's last push was 2026-11-02.

Frequently asked questions

What is meant by IMBA?

In the imba/imba repository, Imba is a friendly full-stack programming language for the web that compiles to JavaScript. It has language-level support for defining and rendering DOM nodes.

Can Imba run on the server?

Yes. Imba runs on both server and client and works with the Node ecosystem; its server example uses express routes and renders Imba tags to HTML strings.

Where do I start with Imba without installing anything?

Imba offers a browser playground at imba.io/try, and the official guide at imba.io is the recommended starting point. Questions go to the Imba Discord.

Official sources

  1. imba/imba on GitHub
  2. License: MIT
  3. Project website
  4. README
  5. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/imba-imba.svg)](https://hysenlabs.com/projects/imba-imba)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/imba-imba.svg)](https://hysenlabs.com/projects/imba-imba)

Was this useful?