Workers SDK Issue Reports

← Back to Dashboard

#8725 `no_bundle` + `alias` does not work as expected

Recommendation:KEEP OPEN
Difficulty:n/a
Reasoning:

Feature request confirmed by maintainer. Aliases processed during bundling phase; when no_bundle=true, alias resolution skipped by design. Valid enhancement request with good reproduction.

Suggested Action:

Update labels to remove "bug", keep "enhancement". Consider adding "feature-request" label.

View on GitHub →

Analysis Report

Issue Review: #8725

Summary

Field Value
Title no_bundle + alias does not work as expected
State OPEN
Created 2025-03-30
Updated 2025-10-30
Labels bug, enhancement
Reporter Version wrangler@4.6.0
Current Version wrangler@4.60.0

Issue Description

When using no_bundle + alias configuration options together, the aliases do not affect script imports. The reporter (@threepointone) notes this may be a feature request rather than a bug, but expects aliases to work regardless.

A minimal reproduction is provided: https://github.com/threepointone/repro-wrangler-no-bundle-alias

Analysis

Maintainer Response

A Cloudflare maintainer (@petebacondarwin) responded on 2025-04-04:

"Nice repro @threepointone - I think this counts as a feature request since aliases are part of the bundling feature in Wrangler."

This confirms the behavior is by design - aliases are implemented as part of the bundling process, so they naturally don't apply when bundling is disabled via no_bundle.

Fix Status

  • No PRs found referencing this issue
  • No changelog entries mentioning #8725
  • No related fixes found for no_bundle + alias combination

Technical Context

The alias configuration in Wrangler is processed during the bundling phase (via esbuild). When no_bundle: true is set, esbuild bundling is skipped entirely, which means alias resolution is also skipped. This is expected behavior, not a bug.

Recommendation

KEEP OPEN - This is a legitimate feature request.

Rationale

  1. Valid feature request: The issue correctly identifies a gap in functionality - users who pre-bundle their code (hence no_bundle) may still want alias resolution
  2. Maintainer acknowledgment: A maintainer has confirmed this is a feature request, not a bug
  3. Clear reproduction: The reporter provided a working reproduction
  4. Active interest: The issue was updated as recently as October 2025

Suggested Actions

  • Update labels to remove "bug" and keep only "enhancement"
  • Consider adding a "feature request" or "needs-design" label
  • The feature would require implementing alias resolution outside the bundling process

Evidence

  • Maintainer comment confirms expected behavior: Comment
  • No PRs or fixes found addressing this feature

Notes & Feedback (0)

No notes yet.

Add Note