npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@brimveyn/aimux-config

v0.6.3

Published

TypeScript configuration API for aimux — keymaps, themes, and backends with a fluent builder.

Downloads

1,565

Readme

@brimveyn/aimux-config

Typed configuration package for @brimveyn/aimux.

Use this package to author aimux.config.ts or aimux.config.js inside an aimux profile directory.

What This Package Does

@brimveyn/aimux-config provides:

  • defineConfig() for typed config authoring
  • the keymap builder API
  • the built-in action catalog
  • theme helpers and built-in theme IDs
  • exported types for config, modes, state, and tooling

It does not launch the app. The aimux runtime loads and consumes the resolved config.

Install

Install it inside an aimux profile directory:

mkdir -p ~/.config/aimux/default
cd ~/.config/aimux/default
bun init -y
bun add -d @brimveyn/aimux-config

Then create:

~/.config/aimux/default/aimux.config.ts

If you use another profile, replace default with that profile name.

Minimal Example

import { defineConfig, actions } from '@brimveyn/aimux-config'

export default defineConfig({
  sessionBar: {
    initialPosition: 'top',
    initialVisible: true,
  },

  keymaps: (k) =>
    k.mode('navigation', (m) => m.map('<C-p>', actions.sessionPicker, 'Workspace picker')),
})

This example only uses surfaces that are wired into the runtime today.

Important: typed config expresses startup intent. Fields such as sessionBar.initialVisible or gitPane.initialMode are reapplied on every launch; runtime UI changes do not write back into aimux.config.ts.

Key Notation

| Notation | Meaning | | ---------------------------------- | -------------------------- | | j | bare character | | J | shifted letter | | <C-n> | Ctrl+N | | <M-x> or <A-x> | Meta or Alt + X | | <C-M-a> | Ctrl+Alt+A | | <CR> | Enter | | <Esc> | Escape | | <Tab> | Tab | | <BS> | Backspace | | <Space> | Space | | <Up> <Down> <Left> <Right> | arrow keys | | <leader> | configured leader chord | | dd | multi-key sequence | | <leader>tn | leader, then t, then n |

Ambiguous prefixes are resolved after the configured timeout.

Keymap Builder

k.leader(key)
  .timeout(ms)
  .mode(id | ids[], configure)

Mode builder methods:

m.map(keys, action, description?)
  .unmap(keys)
  .group(prefix, name, configure)
  .passthrough()

Example with groups and multi-mode bindings:

import { defineConfig, actions } from '@brimveyn/aimux-config'

export default defineConfig({
  keymaps: (k) =>
    k
      .mode('navigation', (m) =>
        m
          .group('<leader>t', 'tabs', (g) =>
            g
              .map('n', actions.newTab, 'New tab')
              .map('r', actions.renameTab, 'Rename tab')
              .map('x', actions.closeTab, 'Close tab')
          )
          .unmap('r')
      )
      .mode(['navigation', 'terminal-input'], (m) =>
        m.map('<C-s>', actions.snippetPicker, 'Snippet picker')
      ),
})

Important Runtime Note About the Leader Key

The shipped runtime defaults use Ctrl+W as the leader key.

The builder itself starts from <Space> internally, but the app merges user config on top of shipped defaults from @brimveyn/aimux. In practice:

  • if you omit .leader(...), the shipped leader stays Ctrl+W
  • if you set another leader such as <C-a>, it overrides the shipped leader
  • do not rely on .leader('<Space>') to switch the runtime leader to Space

See ../../docs/guide/keymaps.md for the full explanation.

Actions

Pre-built actions include:

  • tabs: nextTab, prevTab, newTab, renameTab, closeTab, restartTab
  • workspaces: sessionPicker, switchSessionByIndex(n) and workspace modal actions
  • snippets: snippetPicker, snippet editor and filter actions
  • themes: themePicker, previewTheme, confirmTheme, restoreTheme
  • panes: splitVertical, splitHorizontal, focusPane, resizePane, closePane
  • UI: toggleSidebar, toggleSessionBar, toggleGitPane, resizeGitPane(delta), setGitPaneMode(mode), setGitPanePosition(position)
  • modes: enterInsert, leaveTerminalInput, closeModal, helpModal
  • git: enter git mode, stage, delete or unstage, commit, push

You can also bind a custom ActionFn for dynamic behavior.

Themes

theme is a startup override surface, not the persisted selected theme.

Use it to choose the built-in light or dark family when there is no persisted aimux.json.themeId, and to apply palette overrides on top of the chosen base theme:

import { defineConfig } from '@brimveyn/aimux-config'

export default defineConfig({
  theme: {
    initialMode: 'dark',
    paletteOverrides: {
      primary: '#7dd3fc',
      warning: '#fbbf24',
    },
  },
})

The runtime theme picker persists the selected theme id separately in aimux.json, and that persisted choice wins on restart. See ../../docs/guide/themes.md for picker behavior, palette guidance, and precedence details.

Support Status

| Surface | Status | Notes | | ------------ | ------------------ | ------------------------------------------------------------------------------------ | | keymaps | Supported | Fully registered by the runtime | | sessionBar | Supported | Startup overrides; app-managed runtime state still persists separately | | gitPane | Supported | Startup overrides for placement and rendering; runtime state persists separately | | theme | Supported | theme.initialMode is a startup override; persisted aimux.json.themeId still wins | | themes | Supported | User themes; appear in the picker and power synthesized highlighting | | backends | Typed surface only | Runtime wiring deferred | | sidebar | Typed surface only | Type exists, runtime not currently driven by this field | | hooks | Typed surface only | Type exists, runtime use not currently wired | | snippets | Typed surface only | Runtime currently uses aimux-snippets.json |

Backends Subpath

The package also exports:

@brimveyn/aimux-config/backends

Current helpers:

  • claudeBackend()
  • codexBackend()

These helpers are documented as stubs. Do not treat them as a fully supported runtime backend override system yet.

More Documentation

License

MIT