LogoRelidocs
Reliverse CLI

rse commands

rse commands

rse commands

dler commands

dler ships with a flexible command system (prev. plugins) and 17 built-in commands (from reliverse addons collection).

feel free to create your own commands. commands can be implemented as built-in directly in src/app/<command>/impl/* and then imported from src/app/<command>/cmd.ts; or implemented in your own library and then imported from src/app/<command>/cmd.ts.

if you run just dler — it will display a list of commands which you can launch interactively.

available commands

notes

  • all commands and flags are optional. rse guides you, even if you skip arguments.
  • rse cli is your all-in-one entry point — it includes everything.
  • prefer quick access or running in ci/cd? use specific commands directly.
  • run rse <command> --help to see options and flags.

from bootstrapping projects to ai superpowers — here's what rse cli can do:

rse — build — pub — agg — check — conv — fs — init — inject — libs — merge — migrate — rempts — x — spell — split — pack

0. rse

core commands

  • reliverse cli
    Start the interactive wizard to create or configure a project.

  • reliverse login / reliverse logout
    Log in or out of Reliverse services.

  • reliverse studio
    Launch the Reliverse Studio interface.

  • reliverse --help
    Display all available commands and usage info.

  • rse cli — launch the interactive wizard to create or boost your project.

  • rse logout — logs you out and clears credentials.

  • rse studio — opens the rse studio — the visual brain center of your local rse memory.

  • rse --help — shows all available commands and usage tips.

ai commands

  • rse ai <prompt> — your terminal sidekick. ask questions, get help, or just chat with rse ai.
  • rse ai code <prompt> <paths> — let ai generate or improve code across the given paths.
  • rse ai gen <prompt> — describe an image and ai will create it, saving to your selected upload provider.
  • rse ai lint <prompt> <paths> — smart linting with ai. catches issues, suggests fixes, cleans things up.

init/add commands

  • rse init — kickstart a new minimal rse project. pick your direction and go.
  • rse add (no args) — same as rse init, but with different prompts depending on the folder.
  • rse add <something> — add essentials or extras (api, auth, db, payments, i18n, ai tools, uploaders, forms, etc) — all integrated in seconds.
  • rse add -g <something> (🔜 will be moved to @reliverse/hub) — install global clis (eslint, bun, stripe, code, obsidian, etc) from your terminal.
  • rse add rule <something> — browse and install ai ide rules for rse, cursor, windsurf, copilot, and more — with smart caching and auto-conversion to .mdc if needed.

additional

  • rse clone (docs) — clone a github repo (just paste the link), or convert a webpage into llm-ready content.
  • rse cmod (docs) — apply codemods for quick, safe refactoring (ai or presets).
  • rse env (docs) — generate a .env file from your .env.example with an interactive wizard.
  • rse mrse (docs) — batch-generate multiple rse config files for multiple projects.
  • rse upload (docs) — upload media files (images, etc) to providers like uploadthing and uploadcare.
  • rse sync (coming soon) — sync your local @reliverse/rse memory with your rse ai on reliverse.org.

install

# Install all dependencies
dler install

# Install with workspace filtering
dler install --filter "pkg-*" --filter "!pkg-c"
dler install --filter "./packages/pkg-*"

# Install specific package in filtered workspaces
dler install lodash --filter "pkg-*"

remove

# Remove package from all workspaces
dler remove lodash

# Remove from specific workspaces
dler remove lodash --filter "pkg-*" --filter "!pkg-c"

update

when dler detects that you are in a monorepo, it will uses linked dependencies (--linker).

# Update all dependencies
dler update

# Update with workspace filtering
dler update --filter "pkg-*" --filter "!pkg-c"

# Update specific packages in filtered workspaces
dler update lodash --filter "pkg-*"

1. build

since dler is fully modular, build command is separated for its own build-in plugin as well.

bun dler build ...

supported bundlers

legend:

  • ✅ well tested with big projects
  • 🏗️ not well tested yet
  • 🔜 coming soon

1.1. build binary - Standalone Executable Builder

creates standalone executables for different platforms using bun's --compile feature.

# build for default targets (linux x64, windows x64, macos arm64)
bun dler build binary

# build for all supported platforms
bun dler build binary --targets=all

# build for specific platforms
bun dler build binary --targets=bun-linux-x64,bun-windows-x64

# build with optimization
bun dler build binary --bytecode --minify --sourcemap

# windows-specific options
bun dler build binary --windows-icon=icon.ico --windows-hide-console

# debugging options
bun dler build binary --no-compile --external=c12,terminal-kit,problematic-package

# list all available targets
bun dler build binary --targets=list

supported platforms:

  • linux: x64, x64-baseline, x64-modern, arm64 (with glibc/musl variants)
  • windows: x64, x64-baseline, x64-modern (with .exe extension)
  • macos: x64, arm64

output files:

  • executables: mycli-linux, mycli-windows.exe, mycli-darwin-arm64
  • bundled scripts: mycli-linux.js, mycli-windows.js, mycli-darwin-arm64.js

typical file sizes: 60-120mb per executable (includes bun runtime and dependencies)

2. pub

it already calls build command by itself, so you don't need to run dler build separately.

bun dler pub ...

3. agg

generates aggregator file with content like import { getsomething } from "./utils.js".

# interactively:
dler > "agg"
# non-interactively:
dler agg --input <dir> --out <file> [options]

usage example: if you're exploring the example playground, you can try the following:

  1. open src/libs/sdk/sdk-mod.ts in your ide.
  2. press ctrl+a, then backspace. run the command below and watch the magic happen:
bun tools:agg # shortcut for:
bun src/cli.ts tools --dev --tool agg --input src/libs/sdk/sdk-impl --out src/libs/sdk/sdk-mod.ts --recursive --named --strip src/libs/sdk

4. check

checks your project for common issues and potential improvements. This command performs several types of checks (aka rules of dler):

  • File Extensions: Validates that files have the correct extensions based on their location and module resolution strategy

    • Enforces .ts files in source and JSR distributions
    • Enforces .js files in NPM distributions
    • Supports .css and .json files in all environments
    • Adapts to your module resolution strategy (bundler/nodenext)

  • Path Extensions: Ensures import statements use the correct file extensions

    • Validates import paths match your module resolution strategy
    • Checks for proper extension usage in import statements
    • Supports both relative and absolute imports

  • Dependencies: Identifies missing dependencies in your project

    • Scans all source files for imports
    • Compares against package.json
    • Reports missing dependencies

  • Self-Include: Prevents circular dependencies and self-imports

    • Checks for imports from the main package in dist directories
    • Prevents libraries from importing themselves
    • Allows libraries to import from other libraries

  • Module Resolution: Validates TypeScript module resolution settings

    • Ensures proper moduleResolution in tsconfig.json
    • Supports both "bundler" and "nodenext" strategies
    • Reports configuration issues

  • Dler Config Health: Validates your dler configuration

    • Checks libs main file format
    • Ensures proper configuration structure
    • Reports configuration issues

  • Package.json Validation: Ensures your package.json follows best practices

    • Requires: name, version, type=module, keywords
    • Forbids: bin, exports, files, main, module (they are auto-generated by dler)
    • Helps maintain consistent package configuration
# Fully interactive mode (when no args provided)
dler check

# Mixed mode (some args provided, prompts for the rest)
dler check --directory src
dler check --checks file-extensions,path-extensions
dler check --strict

# Fully automated mode (all args provided)
dler check --directory src --checks file-extensions,path-extensions --strict

# Output in JSON format
dler check --json

arguments:

  • --directory: directory to check (src, dist-npm, dist-jsr, dist-libs/npm, dist-libs/jsr, or all)
  • --checks: comma-separated list of checks to run (missing-deps, file-extensions, path-extensions, dler-config-health, self-include, tsconfig-health, package-json-health)
  • --strict: enable strict mode (requires explicit extensions)
  • --json: output results in JSON format

pro tip:
the command will prompt you only for the arguments you haven't provided. for example, if you specify --directory but not --checks, it will only prompt you to select which checks to run.

how deps check works:

finds missing dependencies in your project by scanning your code for imports and comparing them to your package.json. This command is particularly useful for maintaining clean dependency lists and preventing runtime errors.

what it does:

  • traverses all .js, .jsx, .ts, and .tsx files in your project (by default, in the current directory)
  • detects all used packages, including scoped ones (@org/dep-name)
  • supports both es modules (import ... from "dep") and commonjs (require("dep"))
  • normalizes deep imports like dep/some/file to just dep
  • ignores local/relative imports (./foo, ../bar)
  • skips node_modules, .git, and common build folders
  • compares all used packages to those listed in your package.json
  • shows you which dependencies are missing (not listed)
  • can also show all used dependencies (listed and missing)
  • optionally includes node.js built-in modules in the report
  • outputs results in a readable format or as json
  • exits with error code 1 if missing dependencies are found
  • detects packages that are only in devDependencies but used in production code
  • identifies packages listed in both dependencies and devDependencies

usage examples:

# basic usage - scan current directory
dler deps

# scan a specific directory
dler deps --directory ./my-project

# show all dependencies (both listed and missing)
dler deps --all

# ignore specific patterns
dler deps --ignore "test/**,example/**"

# output in json format
dler deps --json

# include node.js built-in modules
dler deps --include-builtins

# combine options
dler deps --all --directory ./src --include-builtins

missing dependencies are shown only once, even if used in multiple files.
deep imports like dep/some/file or @org/dep/some/thing are always resolved to their root package.

warning types:

  • Missing Dependencies: Packages that are imported but not listed in package.json
  • Dev-only Dependencies: Packages that are only in devDependencies but imported in production code
  • Duplicate Dependencies: Packages listed in both dependencies and devDependencies

5. conv

not yet documented.

6. fs

# simple example:
bun dler fs --mode copy --s "src/**/*.ts" --d "dist"
bun dler fs --mode rm --target "node_modules"
bun dler fs --mode rename --source "index.ts" --destination "index.ts.bak"

# advanced example:
bun dler fs --mode copy --s ".temp/packages/*/lib/**/*" --d "src/libs/sdk/sdk-impl/rules/external"
bun dler fs --mode rm --target "**/node_modules"

7. init

not yet documented.

8. inject

not yet documented.

9. libs

builds and publishes specific subdirectories of your main project as standalone packages.

usage example:
using dler to package src/libs/sdk:

// .config/dler.ts
libsactmode: "main-and-libs",
libsdirdist: "dist-libs",
libsdirsrc: "src/libs",
libslist: {
  "@reliverse/dler-sdk": {
    libdeclarations: true,
    libdescription: "@reliverse/dler without cli",
    libdirname: "sdk",
    libmainfile: "sdk-mod.ts",
    libpkgkeepdeps: false,
    libtranspileminify: true,
  },
},

dler task commands:

  • // dler-replace-line tells dler to grab the contents of ../../types.ts and inject them directly in place of your command definition.

    export * from "../../types"; // dler-replace-line
// or:
export type { specificTypeName1, specificTypeName2 } from "../../types"; // dler-replace-line

  • more magic commands coming soon...

10. merge

merges multiple files into a single file. The command is built for both CI and interactive use, with support for glob patterns and advanced options.

key features:

  • merges text files with optional commented path headers/footers
  • skips binary/media files by default
  • supports both glob patterns and simple paths
  • preserves directory structure when merging to a directory
  • generates source maps for merged output
  • handles file deduplication
  • supports custom separators and comment styles
  • provides interactive mode with prompts
  • includes backup functionality
  • validates file permissions and sizes
  • enforces output path conflict detection
  • handles both single file and directory output modes
  • implements interactive prompts via @reliverse/rempts
  • provides reporting with logging via @reliverse/relinka

usage examples:

# simple example:
bun dler merge --s "src/**/*.ts" --d "dist/merged.ts"

# advanced example:
bun dler merge --s ".temp1/packages/*/lib/**/*" --d ".temp2/merged.ts" --sort "mtime" --header "// Header" --footer "// Footer" --dedupe

arguments:

  • --s: Input glob patterns (array)
  • --d: Output file path or directory
  • --ignore: Extra ignore patterns (array)
  • --format: Fallback extension when output path is omitted (default: "txt")
  • --stdout: Print to stdout
  • --noPath: Don't inject relative path below each file
  • --pathAbove: Print file path above each file's content (default: true)
  • --separator: Custom separator (default: "\n\n")
  • --comment: Custom comment prefix (e.g. '# ')
  • --forceComment: Force custom comment prefix for all file types
  • --batch: Disable interactive prompts (CI/non-interactive mode)
  • --recursive: Recursively process all files in subdirectories (default: true)
  • --preserveStructure: Preserve source directory structure in output (default: true)
  • --increment: Attach an incrementing index to each output filename
  • --concurrency: Number of concurrent file operations (default: 8)
  • --sort: Sort files by: name, path, mtime, none (default: path)
  • --dryRun: Show what would be done, but don't write files
  • --backup: Backup output files before overwriting
  • --dedupe: Remove duplicate file contents in merge
  • --header: Header text to add at the start of merged output
  • --footer: Footer text to add at the end of merged output
  • --select-files: Prompt for file selection before merging
  • --interactive: Enable interactive mode with prompts
  • --depth: Depth level to start processing from (default: 0)
  • --sourcemap: Generate source map for the merged output

implementation details:

  • uses magic-string for efficient string manipulation and source map generation
  • leverages @reliverse/reglob for glob pattern matching
  • implements concurrent file operations with p-map
  • provides file type detection and appropriate comment styles
  • includes safety checks for file sizes and permissions
  • handles both single file and directory output modes
  • implements interactive prompts via @reliverse/rempts
  • provides reporting with logging via @reliverse/relinka

11. migrate

helps migrate between different libraries and module resolution strategies. currently supports:

  • anything-bun: migrate Node.js projects to Bun runtime
  • path-pathkit: migrate from node:path and unjs/pathe to pathkit library
  • fs-relifso: migrate from node:fs and fs-extra to relifso library
  • nodenext-bundler: migrate between module resolution strategies
  • readdir-glob: migrate from fs.readdir to globby for better file system operations

path-pathkit features:

  • Migrates from both pathe and node:path to @reliverse/pathkit
  • Handles both default and named exports
  • Supports multi-line imports
  • Converts require statements
  • Updates package.json dependencies

fs-relifso features:

  • Migrates from both node:fs and fs-extra to @reliverse/relifso
  • Handles both default and named exports
  • Supports multi-line imports
  • Converts require statements
  • Updates package.json dependencies
  • Preserves import structure and formatting

anything-bun features:

  • Migrates Node.js imports to use node: prefix
  • Replaces npm/yarn/pnpm features with bun equivalents
  • Converts to Bun-native APIs:
    • Database: pg/postgres → Bun.sql, sqlite3 → bun:sqlite
    • Redis: redis/ioredis → Bun.redis
    • Utilities: glob → Bun.Glob, bcrypt/argon2 → Bun.password
    • Testing: jest/vitest → bun:test
    • FFI: node-ffi → bun:ffi
  • Transforms file operations to Bun.file API
  • Converts Express apps to Bun.serve
  • Updates package.json scripts and dependencies
  • Generates Bun configuration files
  • Creates Dockerfile for Bun deployment

readdir-glob features:

  • Migrates from fs.readdir and fs.readdirSync to globby
  • Handles both synchronous and asynchronous readdir operations
  • Supports fs.promises.readdir migration
  • Adds globby import if not present
  • Updates package.json with globby dependency
  • Preserves target directory paths
  • Maintains async/await usage

usage examples:

# Preview changes without applying them
dler migrate --lib readdir-glob --dryRun

# Apply changes
dler migrate --lib readdir-glob

# Migrate specific project
dler migrate --lib readdir-glob --project ./my-app

module resolution targets:

  • nodenext: adds .js extensions to imports and updates tsconfig
  • bundler: removes extensions from imports and updates tsconfig

usage examples:

# Migrate from node:path and/or pathe to pathkit
dler migrate --lib path-pathkit

# Migrate from node:fs and/or fs-extra to relifso
dler migrate --lib fs-relifso

# Migrate to nodenext module resolution
dler migrate --lib nodenext-bundler --target nodenext

# Migrate to bundler module resolution
dler migrate --lib nodenext-bundler --target bundler

# Preview changes without applying them
dler migrate --lib nodenext-bundler --target nodenext --dryRun

what it does:

  • updates import statements in your code
  • modifies tsconfig.json settings
  • updates package.json type field
  • provides a dry run option to preview changes
  • handles both relative and alias imports
  • supports both .ts and .tsx files

console-relinka:

@reliverse/relinka's best friend. Converts between different logging formats (console, consola method/object, and relinka's function/method/object styles).

# Basic usage
dler relinka --input <file> --from <source> --to <target>

# Examples:
# Convert console.log to relinka function style
dler relinka --input src/app.ts --from console --to relinkaFunction

# Convert consola method to relinka method style
dler relinka --input src/app.ts --from consolaMethod --to relinkaMethod

# Convert between relinka styles
dler relinka --input src/app.ts --from relinkaMethod --to relinkaObject

# Convert to consola object style
dler relinka --input src/app.ts --from relinkaFunction --to consolaObject

Supported formats:

  • console: Standard console logging (console.log(message, ...args))
  • consolaMethod: Consola method style (consola.log(message, ...args))
  • consolaObject: Consola object style (consola({ level, message, title?, args? }))
  • relinkaFunction: Relinka function style (relinka("level", message, ...args))
  • relinkaMethod: Relinka method style (relinka.level(message, ...args))
  • relinkaObject: Relinka object style (relinka({ level, message, title?, args? }))

Special features:

  • Preserves additional arguments in all formats
  • Handles special box format with title and message
  • Maintains proper escaping and formatting
  • Supports conversion between any combination of formats
  • Supports both consola method and object styles

next steps after migration:

  • for path-pathkit:

    1. run 'bun install' to install @reliverse/pathkit
    2. test your application
    3. consider using advanced pathkit features

  • for fs-relifso:

    1. run 'bun install' to install @reliverse/relifso
    2. test your application
    3. review any file system operations that might need manual updates

  • for nodenext-bundler:

    1. test your application
    2. ensure your build tools support the new module resolution
    3. review any warnings in the migration output

  • for anything-bun:

    1. run 'bun install' to install dependencies with Bun
    2. test your application thoroughly
    3. review async/await usage in converted file operations
    4. update any custom database queries to use Bun.sql syntax
    5. review and update any custom middleware in Express apps

  • for readdir-glob:

    1. run 'bun install' to install globby
    2. test your application
    3. review any file system operations that might need manual updates
    4. consider using globby's advanced features like pattern matching and recursive searching

12. rempts

@reliverse/rempts's best friend. learn more in its docs.

bun dler rempts
bun dler rempts --init cmd1 cmd2

13. x

dler x — your package manager — refined.

bun dler x ...

14. magic

programmatic usage:

function main() {
  // may be useful when your cli is a project bootstrapper tool like @reliverse/rse
  // so you can apply spells to each bootstrapped by you cli project's file
  await applyMagicSpells(["my-target-dir"]);
}
await main();

or, call it from dler config's hook:

{
  hooksAfterBuild: [
    async () => {
      // useful when you want to apply spells right after dler's build
      await applyMagicSpells(["dist-jsr", "dist-npm", "dist-libs"]);
    }
  ],
}

or, use dler magic:

dler magic --targets "my-target-dir"

available spell types:

  • replace-line — injects contents from one file into another
  • replace-range — replaces a range of lines with content from another file
  • rename-file — renames the current file
  • remove-comment — removes a specific comment from code
  • remove-line — removes a specific line from code
  • remove-file — deletes the current file
  • transform-content — applies a transformation to the file content
  • transform-line — applies a transformation to a specific line
  • copy-file — copies the current file to a new location
  • move-file — moves the current file to a new location
  • insert-at — inserts content at a specific position in the file
  • insert-before — inserts content before a specific line
  • insert-after — inserts content after a specific line
  • conditional-execute — executes spells conditionally

params:

params are optional and comma-separated.

  • hooked (boolean, default: true)
    • true: disables default behavior, so you can trigger the spell yourself (e.g. from your own cli function)
    • false: dler handles the spell automatically at postbuild
  • startLine (number) — line number to start the operation (for range operations)
  • endLine (number) — line number to end the operation (for range operations)
  • condition (string) — condition to check before executing the spell
  • skipIfMissing (boolean) — whether to skip the spell if the target file doesn't exist
  • createDir (boolean) — whether to create the target directory if it doesn't exist

usage examples:

  • export * from "../../types"; // dler-replace-line — injects file contents at this line (hooked=true by default)
  • // @ts-expect-error dler-remove-comment — removes just this comment (hooked=true by default)
  • // dler-remove-line — removes this line (hooked=true by default)
  • // dler-remove-file — deletes this file (hooked=true by default)
  • // dler-rename-file-"tsconfig.json"-{hooked=false} — renames this file (runs at postbuild because hooked=false)
  • // dler-replace-range-"../../types.js"-{startLine=1,endLine=5} — replaces lines 1-5 with content from types.js
  • // dler-transform-line-"return line.toUpperCase()" — transforms the line to uppercase
  • // dler-insert-before-"import { x } from 'y';" — inserts import statement before this line
  • // dler-insert-after-"export { x };" — inserts export statement after this line
  • // dler-conditional-execute-{condition="content.includes('TODO')"} — executes spells only if file contains TODO

using hooked=false:

  • // dler-rename-file-"tsconfig.json"-{hooked=false} — renames the file immediately at postbuild (not hooked)

triggering spells:

from dler's cli:

  • dler spell --trigger rename-file,... --files tsconfig.json,...
  • dler spell --trigger all
  • dler spell

from your own code:

await dler.spell({ spells: ["rename-file"], files: [] });
await dler.spell({}) // all spells, all files
spells: ["all"] // means all spells
spells: [] // also means all spells
files: [] // means all files

p.s. see how rse cli uses hooked=true

Contributors: Please check the docs/cmds/SPELLS.md file for more technical details.

15. split

splits your code/text file into multiple files.

bun dler split ...

16. pack

packs a directory of templates into TypeScript modules. This command is useful for creating reusable template packages that can be distributed and used by other projects.

key features:

  • Converts directory structure into TypeScript modules
  • Handles binary files with automatic hashing and storage
  • Preserves JSON comments and formatting
  • Supports custom whitelabeling
  • Generates type-safe template definitions
  • Creates an aggregator module for easy imports
  • Tracks file metadata (update time and content hash)
  • Supports selective file updates
  • Handles file conflicts gracefully
  • Preserves JSON type information for package.json and tsconfig.json

usage examples:

# Basic usage
dler pack --dir ./templates --output ./dist-templates

# With custom whitelabel
dler pack --dir ./templates --output ./dist-templates --whitelabel MYAPP

# Update specific files only
dler pack --dir ./templates --output ./dist-templates --files "src/index.ts,src/config.ts"

# Force overwrite existing files
dler pack --dir ./templates --output ./dist-templates --force

# Update mode (default: true)
dler pack --dir ./templates --output ./dist-templates --update

arguments:

  • --dir: Directory containing templates to process (required)
  • --output: Output directory for generated modules (default: "my-templates")
  • --whitelabel: Custom prefix to use instead of 'DLER' (default: "DLER")
  • --cdn: Remote CDN for binary assets upload (not yet implemented)
  • --force: Force overwrite existing files (default: false)
  • --update: Update existing templates and add new ones (default: true)
  • --files: Comma-separated list of specific files to update
  • --lastUpdate: Override lastUpdate timestamp

output structure:

output/
├── impl/
│   ├── binaries/ # binary files stored with hash-based names (dler reads/writes this dir when --cdn is not used)
│   │   └── [hashed-files]
│   ├── template1.ts
│   └── template2.ts
├── types.ts
└── mod.ts

--unpack:

creates file structure from packed templates. This command is the counterpart to pack and is used to extract and restore template files from a packed template package.

key features:

  • Restores complete directory structure from packed templates
  • Handles binary files with automatic lookup
  • Preserves JSON comments and formatting
  • Supports custom output locations
  • Maintains file permissions and structure
  • Validates template integrity
  • Supports cleanup of existing template files
  • Provides dry-run mode for previewing changes
  • Handles empty directory cleanup

usage examples:

# Basic usage
dler pack ./dist-templates --output ./my-project --unpack

# With custom output directory
dler pack ./dist-templates --output ./custom-location --unpack

# Preview changes without applying
dler pack ./dist-templates --output ./my-project --dry-run --unpack

# Clean up existing template files before unpacking
dler pack ./dist-templates --output ./my-project --cleanup --unpack

arguments:

  • templatesDir: Directory containing mod.ts (required)
  • --output: Where to write files (default: "unpacked")
  • --cdn: Remote CDN base for binary assets download (not yet implemented)
  • --cleanup: Clean up template files before unpacking (default: false)
  • --dry-run: Preview changes without applying them (default: false)

implementation details:

  • Uses jiti for dynamic template file loading
  • Implements template validation and type checking
  • Provides detailed error handling and reporting
  • Handles file system operations safely
  • Preserves JSON comments and formatting
  • Supports binary file restoration
  • Cleans up empty directories after unpacking
  • Validates template structure before unpacking

api (for advanced usage)

the sdk lets you build custom dler cli plugins or even extend your own cli tools.

bun add @reliverse/dler-sdk

usage example: @reliverse/rse leverages this sdk to extend its functionality.

17. update

updates your project's dependencies to the latest version.

updates not only dependencies/devDependencies/peerDependencies/optionalDependencies, but also monorepo catalogs.

bun dler update

params:

  • --with-check-script (boolean) — runs bun check after updating (exclusive for bun environment at the moment)

example package.json:

{
  "scripts": {
    "latest": "bun dler update --with-check-script",
    "check": "tsc --noEmit && eslint --cache --fix . && biome check --fix --unsafe . && knip"
  }
}

coming soon:

  • recursive lookup for deps in multiple package.json files (e.g. monorepo; or case when you have C:/foo/bar1/package.json and C:/foo/bar2/package.json and using dler update in C:/foo).

workspaces and catalogs

dler has full workspaces and catalogs support for the package management commands. Catalog logic is similar to Bun across all package management commands.

Catalog Features:

1. Install Dependencies as Catalogs

# Add to default catalog
dler install react react-dom --as-catalog default

# Add to named catalog
dler install jest testing-library --as-catalog testing
dler install webpack babel --as-catalog build --catalog-name build

# With workspace filtering
dler install lodash --as-catalog default --filter "pkg-*"

2. Remove Dependencies from Catalogs

# Remove from default catalog
dler remove react react-dom --from-catalog default

# Remove from named catalog
dler remove jest --from-catalog testing
dler remove webpack --from-catalog build --catalog-name build

3. List Catalogs

# List all catalogs and their dependencies
dler catalog list
dler catalog ls

4. Update Catalogs

# Update all catalog dependencies to latest versions
dler update --update-catalogs

Technical Implementation:

Smart Version Management

  • Dler automatically fetches latest versions from npm registry
  • Uses ^ and ~ prefixes for semver compatibility
  • Handles scoped packages correctly

Catalog Structure Support:

Default Catalog

{
  "workspaces": {
    "packages": ["packages/*"],
    "catalog": {
      "react": "^19.0.0",
      "react-dom": "^19.0.0"
    }
  }
}

Named Catalogs

{
  "workspaces": {
    "packages": ["packages/*"],
    "catalogs": {
      "testing": {
        "jest": "^30.0.0",
        "testing-library": "^14.0.0"
      },
      "build": {
        "webpack": "^5.88.2",
        "babel": "^7.22.10"
      }
    }
  }
}

Usage Examples:

Setting up a React Monorepo with Catalogs:

# 1. Add core React dependencies to default catalog
dler install react react-dom react-router-dom --as-catalog default

# 2. Add build tools to named catalog
dler install webpack babel --as-catalog build

# 3. Add testing tools to named catalog
dler install jest react-testing-library --as-catalog testing

# 4. List all catalogs
dler catalog list

# 5. Update all catalogs to latest versions
dler update --update-catalogs

Workspace Package Usage:

// packages/app/package.json
{
  "dependencies": {
    "react": "catalog:",
    "react-dom": "catalog:",
    "react-router-dom": "catalog:"
  },
  "devDependencies": {
    "webpack": "catalog:build",
    "jest": "catalog:testing"
  }
}

Advanced Operations:

# Add dependencies to specific workspaces as catalogs
dler install lodash --as-catalog default --filter "pkg-*" --filter "!pkg-c"

# Remove dependencies from catalogs in filtered workspaces
dler remove typescript --from-catalog default --filter "pkg-*"

# Update catalogs and then install
dler update --update-catalogs
dler install

Benefits:

  1. Consistency: Ensures all packages use the same version of critical dependencies
  2. Maintenance: Update a dependency version in one place instead of across multiple package.json files
  3. Clarity: Makes it obvious which dependencies are standardized across your monorepo
  4. Simplicity: No need for complex version resolution strategies or external tools
  5. Workspace Integration: Seamlessly works with workspace filtering
  6. Cross-Package Manager: Works with Bun (full support) and provides helpful messages for others

Reliverse CLI

A powerful CLI that helps you effortlessly create new web projects, manage existing ones, and apply advanced, automated modifications to your codebase.

rse todo

rse todo