GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — `deploy-url` is not prepended to imported file url when using `file` loader in `esbuild` · Issue #32789 · angular/angular-cli

deploy-url is not prepended to imported file url when using file loader in esbuild #32789

New issue
Copy link
New issue
Copy link
Open
Open
deploy-url is not prepended to imported file url when using file loader in esbuild#32789
Copy link
Labels
angular/build:applicationarea: @angular/buildfreq1: lowOnly reported by a handful of users who observe it rarelyOnly reported by a handful of users who observe it rarelygemini-triagedLabel noting that an issue has been triaged by geminiLabel noting that an issue has been triaged by geminiseverity3: brokentype: bug/fix

Description

@pshurygin
pshurygin
opened on Mar 18, 2026
Issue body actions

Command

build

Is this a regression?

  • Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

any webpack-based build

Description

When using Angular v21 with the new esbuild builder, and using a file loader configured for certain file types (like SVG) the --deploy-url argument passed into the build command does not get prepended to the URL returned when importing a file of the said type, and there is no way to configure it to do so.

This was properly working previously with webpack, when loading of the SVG assets was configured with a rule like this:

{
  test: /\.svg$/,
  type: 'asset/resource',
  generator: {
    filename: '[name][hash][ext]',
  },
}

Looks like with esbuild there is no way to achieve the same result, apart from manually adding deploy-url to imported URLs in runtime.

Minimal Reproduction

  1. Use esbuild application builder
  2. Configure angular.json to use file loader to import a certain file type:
"loader": {
  ".svg": "file"
},
  1. Build application using ng build --deploy-url=/my-deploy-url/
  2. Import some SVG file in the app:
import mySvgUrl from './my-image.svg';
  1. Observe: mySvgUrl does not have /my-deploy-url/ prepended to it

Exception or Error

No error

Your Environment

Angular CLI       : 21.2.2
Angular           : 21.2.4
Node.js           : 24.8.0
Package Manager   : npm 11.6.0
Operating System  : darwin arm64

┌───────────────────────────────────┬───────────────────┬───────────────────┐
│ Package                           │ Installed Version │ Requested Version │
├───────────────────────────────────┼───────────────────┼───────────────────┤
│ @angular/animations               │ 21.2.4            │ 21.2.4            │
│ @angular/build                    │ 21.2.2            │ 21.2.2            │
│ @angular/cdk                      │ 21.2.2            │ 21.2.2            │
│ @angular/cli                      │ 21.2.2            │ 21.2.2            │
│ @angular/common                   │ 21.2.4            │ 21.2.4            │
│ @angular/compiler                 │ 21.2.4            │ 21.2.4            │
│ @angular/compiler-cli             │ 21.2.4            │ 21.2.4            │
│ @angular/core                     │ 21.2.4            │ 21.2.4            │
│ @angular/elements                 │ 21.2.4            │ 21.2.4            │
│ @angular/forms                    │ 21.2.4            │ 21.2.4            │
│ @angular/localize                 │ 21.2.4            │ 21.2.4            │
│ @angular/platform-browser         │ 21.2.4            │ 21.2.4            │
│ @angular/platform-browser-dynamic │ 21.2.4            │ 21.2.4            │
│ @angular/router                   │ 21.2.4            │ 21.2.4            │
│ rxjs                              │ 7.8.2             │ 7.8.2             │
│ typescript                        │ 5.9.3             │ 5.9.3             │
│ vitest                            │ 4.0.18            │ 4.0.18            │
│ zone.js                           │ 0.16.0            │ 0.16.0            │
└───────────────────────────────────┴───────────────────┴───────────────────┘
Reacted by Yuriy Grunin

Activity

  1. angular-robot
    added
    area: @angular-devkit/build-angular
    gemini-triagedLabel noting that an issue has been triaged by geminiLabel noting that an issue has been triaged by gemini
    on Mar 18, 2026
  2. alan-agius4
    added
    type: bug/fix
    freq1: lowOnly reported by a handful of users who observe it rarelyOnly reported by a handful of users who observe it rarely
    severity3: broken
    angular/build:application
    area: @angular/build
    and removed
    area: @angular-devkit/build-angular
    on Mar 18, 2026
  3. maruthang
    added a commit that references this issue on Mar 27, 2026

    fix(@angular/build): prepend deploy-url to file loader output paths

    This issue will close once commit 076388e is merged into the 'main' branch.
    076388e

  4. maruthang commented on Mar 27, 2026

    @maruthang
    maruthang
    on Mar 27, 2026 · Hidden as spam
    show commentMore actions
  5. maruthang
    added a commit that references this issue on Mar 27, 2026

    fix(@angular/build): prepend deploy-url to file loader output paths

    This issue will close once commit 0760143 is merged into the 'main' branch.
    0760143

  6. pshurygin commented on Apr 1, 2026

    @pshurygin
    pshurygin
    on Apr 1, 2026
    Author
    More actions

    @clydin I see this mentioned in the linked pull request

    Further information is needed from the originating issue regarding a specific use case and reproduction before changes can made.

    Yet the reproduction is right there in the PR description. And the use case should be pretty clear: I want to get a proper URL of my static images to be used in a component code(eg in an img.src), yet the file loader gives me an incorrect URL when I build the app with set deploy-url. Also, this is a regression from the webpack builder, which handled this case properly.

  7. maruthang
    added a commit that references this issue on Apr 6, 2026

    fix(@angular/build): prepend deploy-url to file loader output paths

    This issue will close once commit fa7f43b is merged into the 'main' branch.
    fa7f43b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    angular/build:applicationarea: @angular/buildfreq1: lowOnly reported by a handful of users who observe it rarelyOnly reported by a handful of users who observe it rarelygemini-triagedLabel noting that an issue has been triaged by geminiLabel noting that an issue has been triaged by geminiseverity3: brokentype: bug/fix

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions
      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.