Technology1 min read

Nudeps: bundler-like imports, none of the baggage

By · Published by Everything Blog

In short

The tool addresses dependency management issues spotlighted in the State of JS 2025 survey by utilizing a light-build workflow. It lets developers install packages through npm and import them directly by name, completely bypassing traditional code-rewriting processes. While it cannot compile languages like TypeScript or JSX, it serves basic resolution needs and complements static site generators or island architectures. Setup is streamlined through a single installation command and an import map script tag added to the HTML.

Key points

  • Dependency friction highlighted in the State of JS 2025 survey drove the creation of this…: Dependency friction highlighted in the State of JS 2025 survey drove the creation of this lightweight build alternative.
  • Browsers natively demand URLs for imports, but import maps and vendoring permit standard…: Browsers natively demand URLs for imports, but import maps and vendoring permit standard bare package specifiers.
  • The utility focuses solely on dependency imports and must be combined with other tools to…: The utility focuses solely on dependency imports and must be combined with other tools to compile JSX or TypeScript.

Sources checked by our analysis pipeline: 1

Bundlers are currently the only way to use dependencies without losing our sanity, but introduce complexity and overhead. Today, I’m releasing a new type of lightweight build tool that challenges that.

The goal is light-build, not no-build

You npm install

a package (e.g. vue

), you write import { createApp } from "vue"

, and it works — as long as there is a bundler in between.

Without one, the browser has no idea what "vue"

is: it only understands URLs, and node_modules/

was never meant to be deployed.

So even the simplest project ends up needing a bundler, only so it can use dependencies instead of reinventing the wheel.

But bundlers add a significant tax. They process every single file, introduce several layers of abstraction between source and deployment, and these abstractions often leak: things that work fine in the browser can break in the build.

Earlier this year, I published Web dependencies are broken: Can we fix them? that discusses this from a platform architecture perspective. Besides the architectural concerns, the complexity is an active developer pain point:…

Technology