🧬 dler (prev. relidler) • build/publish/improve ts/js libs/cli/apps

sponsor — discord — github — npm

@reliverse/dler (/ˈdiː.lər/, dealer) is a flexible, unified, and fully automated bundler for typescript/javascript projects that doubles as an npm/jsr publishing tool. beyond bundling, dler serves as a comprehensive codemod toolkit for modern typescript/javascript development.

features

🚀 core power

• unjs/unbuild drop-in with different powerful capabilities like publishing
• automated publishing to npm/jsr registries with intelligent workflow management
• reliable builds with comprehensive typescript/javascript support and error handling
• smart versioning with automatic version bumps and semantic release integration
• zero configuration eliminates package.json maintenance headaches forever

⚡ developer experience

• performance optimized for speed with modern build pipelines and caching
• 16 built-in commands — comprehensive dler commands for every workflow
• path resolution magic converts typescript aliases to relative imports automatically
• highly configurable via dedicated configuration files with sensible defaults
• dual interface — cli for everyday use, sdk for advanced programmatic control

🔧 advanced capabilities

• clean distribution builds automatically removes internal logs and debug code
• monorepo ready with experimental libs feature for multi-library projects
• magic spells — extensible plugin system for custom build transformations
• codemod toolkit — powerful code transformation utilities built-in

🎯 perfect for

dler excels at managing both build and publish workflows, making it ideal for:

• cli tool creators and maintainers
• project bootstrappers (like rse)
• library authors seeking streamlined workflows
• teams wanting consistent build processes

🔜 coming soon

full monorepo system with advanced dependency management and cross-package optimization.

supported bundlers

• ✅ mkdist
• ✅ jsr
• 🏗️ copy
• 🏗️ bun
• 🏗️ rollup
• 🏗️ untyped
• 🔜 tsdown
• 🔜 copy (prev. jsr)

legend:

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

getting started

make sure you have git, node.js, and bun/pnpm/yarn/npm (bun is highly recommended) are installed. then:

0. try the playground

💡 tip: want to test dler before integrating it into your project? clone the dler repo and build it using dler itself!

1git clone https://github.com/reliverse/dler.git
2cd dler
3bun i
4bun dev # bun src/cli.ts --dev

1. install dler

install as dev dep (recommended):

1bun add -D @reliverse/dler
2# or update as needed:
3bun update --latest

and/or install globally:

1bun add -g @reliverse/dler
2# or update as needed:
3bun i -g update --latest

• when installed globally: use dler anywhere.
• when installed as dev dep: use with package manager name prefix, e.g. bun dler, inside your project directory.

2. prepare your project

a. configure .gitignore:

1echo "dist*" >> .gitignore
2echo "logs" >> .gitignore

b. add ".config/**/*.ts" to include in tsconfig.json:

1"include": [".config/**/*.ts", ...]

c. package.json:

1"scripts": {
2  "build": "dler build", // this is optional
3  "pub": "dler pub" // this does build+publish
4}

d. initialize config:

1bun dler # if installed as dev dep
2dler # if installed globally

• the .config/dler.ts file is automatically created on first run.

e. optionally, customize .config/dler.ts:

• it's recommended to customize this file according to your needs.
• you can check an example config here: .config/dler.ts
• if you want to build files which have extensions other than .ts and .js, you can customize buildPreExtensions array (example: ["ts", "js", "vue", "tsx", "jsx"]).
• if you want to exclude some files from being built, you can customize buildTemplatesDir string (example: "templates"). by placing them in this directory, they will not be built, whole directory will be copied from e.g. src/foo/templates to dist-*/bin/foo/templates as-is.

3. run and enjoy

1bun dler [build|pub|--help] # if installed as dev dep
2dler [build|pub|--help] # if installed globally

(run just dler to see an interactive list of commands)

dler commands

dler ships with a flexible command system (prev. plugins) and 16 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

build — pub — agg — check — conv — copy — init — inject — libs — merge — migrate — rempts — rename — spell — split — pack

1. build

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

1bun dler build ...

2. pub

pub command is separated for its own build-in plugin as well.

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

1bun dler pub ...

3. agg

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

1# interactively:
2dler > "agg"
3# non-interactively:
4dler 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:

1bun tools:agg # shortcut for:
2bun 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

1# Fully interactive mode (when no args provided)
2dler check
3
4# Mixed mode (some args provided, prompts for the rest)
5dler check --directory src
6dler check --checks file-extensions,path-extensions
7dler check --strict
8
9# Fully automated mode (all args provided)
10dler check --directory src --checks file-extensions,path-extensions --strict
11
12# Output in JSON format
13dler 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:

1# basic usage - scan current directory
2dler deps
3
4# scan a specific directory
5dler deps --directory ./my-project
6
7# show all dependencies (both listed and missing)
8dler deps --all
9
10# ignore specific patterns
11dler deps --ignore "test/**,example/**"
12
13# output in json format
14dler deps --json
15
16# include node.js built-in modules
17dler deps --include-builtins
18
19# combine options
20dler 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. copy

1# simple example:
2bun dler copy --s "src/**/*.ts" --d "dist"
3
4# advanced example:
5bun dler copy --s ".temp/packages/*/lib/**/*" --d "src/libs/sdk/sdk-impl/rules/external"

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:

1// .config/dler.ts
2libsactmode: "main-and-libs",
3libsdirdist: "dist-libs",
4libsdirsrc: "src/libs",
5libslist: {
6  "@reliverse/dler-sdk": {
7    libdeclarations: true,
8    libdescription: "@reliverse/dler without cli",
9    libdirname: "sdk",
10    libmainfile: "sdk-mod.ts",
11    libpkgkeepdeps: false,
12    libtranspileminify: true,
13  },
14},

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.

  1export * from "../../types"; // dler-replace-line
  2// or:
  3export 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:

1# simple example:
2bun dler merge --s "src/**/*.ts" --d "dist/merged.ts"
3
4# advanced example:
5bun 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:

1# Preview changes without applying them
2dler migrate --lib readdir-glob --dryRun
3
4# Apply changes
5dler migrate --lib readdir-glob
6
7# Migrate specific project
8dler 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:

1# Migrate from node:path and/or pathe to pathkit
2dler migrate --lib path-pathkit
3
4# Migrate from node:fs and/or fs-extra to relifso
5dler migrate --lib fs-relifso
6
7# Migrate to nodenext module resolution
8dler migrate --lib nodenext-bundler --target nodenext
9
10# Migrate to bundler module resolution
11dler migrate --lib nodenext-bundler --target bundler
12
13# Preview changes without applying them
14dler 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).

1# Basic usage
2dler relinka --input <file> --from <source> --to <target>
3
4# Examples:
5# Convert console.log to relinka function style
6dler relinka --input src/app.ts --from console --to relinkaFunction
7
8# Convert consola method to relinka method style
9dler relinka --input src/app.ts --from consolaMethod --to relinkaMethod
10
11# Convert between relinka styles
12dler relinka --input src/app.ts --from relinkaMethod --to relinkaObject
13
14# Convert to consola object style
15dler 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.

1bun dler rempts
2bun dler rempts --init cmd1 cmd2

13. rename

1bun dler rename ...

14. magic

programmatic usage:

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

or, call it from dler config's hook:

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

or, use dler magic:

1dler 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:

1await dler.spell({ spells: ["rename-file"], files: [] });
2await dler.spell({}) // all spells, all files
3spells: ["all"] // means all spells
4spells: [] // also means all spells
5files: [] // 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.

1bun 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:

1# Basic usage
2dler pack --dir ./templates --output ./dist-templates
3
4# With custom whitelabel
5dler pack --dir ./templates --output ./dist-templates --whitelabel MYAPP
6
7# Update specific files only
8dler pack --dir ./templates --output ./dist-templates --files "src/index.ts,src/config.ts"
9
10# Force overwrite existing files
11dler pack --dir ./templates --output ./dist-templates --force
12
13# Update mode (default: true)
14dler 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:

1output/
2├── impl/
3│   ├── binaries/ # binary files stored with hash-based names (dler reads/writes this dir when --cdn is not used)
4│   │   └── [hashed-files]
5│   ├── template1.ts
6│   └── template2.ts
7├── types.ts
8└── 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:

1# Basic usage
2dler pack ./dist-templates --output ./my-project --unpack
3
4# With custom output directory
5dler pack ./dist-templates --output ./custom-location --unpack
6
7# Preview changes without applying
8dler pack ./dist-templates --output ./my-project --dry-run --unpack
9
10# Clean up existing template files before unpacking
11dler 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.

1bun add @reliverse/dler-sdk

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

related

special thanks to the project that inspired @reliverse/dler:

• unjs/unbuild

contributors

helper scripts

• libs:pack: Creates two templates, cfg and sdk, based on dist-libs directory structure (using dler pack command).
• libs:unpack: Creates a project structure using all templates from the cfg and sdk templates (using dler unpack command).
• libs:example: Since libs:unpack's serves as a dist-libs mock, then libs:example helps easily test dler's features like resolveAllCrossLibs().

notes

• <src | dist-npm | dist-jsr>/libs/<lib-name>/<files live here> === dist-libs/<lib-name>/<jsr | npm>/bin/<files live here>

todo

• dist-*-> dist/dist-*
• implement stable regular build and publish
• implement stable library build and publish
• achieve full drop-in replacement for unbuild
• support auto migration from build.config.ts
• support configuration via .config/rse.{ts,jsonc} 🤔
• make config file fully optional with sensible defaults
• use dler remdn (@reliverse/remdn) to generate npm/jsr specific readme and a single docs dir for a whole project (only readmes will be published, docs are only stored in project's source cpde and can be deployed to user's website)
• allow plugins to extend dler's defineconfig (hooksBeforeBuild and hooksAfterBuild are now available, plugin's options can be passed directly to plugin's params, e.g. hooksBeforeBuild: [ async () => { await myCoolPlugin({ /* plugin's options */ }); } ],)
• at the moment any bundler like mkdist can be called using bun, but bun's own bundler is not yet fully supported
• support all well-known package managers (currently only bun is fully supported)

support

• if dler saves you time and effort, please consider supporting its development: github sponsors;
• even a simple star on github shows your love. thank you!

license

🩷 mit © 2025 blefnk nazar kornienko