[Bug]: can not set publicPath

[yuyu668668]

Describe the bug

• when I set the publicPath, it not work.

`import type { StorybookConfig } from '@storybook/angular';

const config: StorybookConfig = {
stories: ['../**/*.@(mdx|stories.@(js|jsx|ts|tsx))'],
addons: [],
framework: {
name: '@storybook/angular',
options: {},
},
core: {
builder: {
name: '@storybook/builder-webpack5',
options: {
fsCache: true,
},
},
},
webpackFinal: async (config, { configType }) => {
// Set publicPath to /fe/ for both development and production
if (config.output) {
config.output.publicPath = '/storybook/';
}

return config;

},
managerHead: (head) => `
${head}

`, previewHead: (head) => ` ${head} `, };

export default config;`

when open browser, it will error.
:4401/storybook/sb-manager/globals-runtime.js:1 Failed to load resource: the server responded with a status of 404 (Not Found)
:4401/storybook/sb-manager/runtime.js:1 Failed to load resource: the server responded with a status of 404 (Not Found)
:4401/storybook/favicon.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found)

Reproduction link

https://storybook.js.org/docs/api/main-config/main-config-webpack-final

Reproduction steps

1. set the publicPath
2. run the storybook

System

System:
│  OS: Windows 11 10.0.26200
│  CPU: (12) x64 12th Gen Intel(R) Core(TM) i5-12450H
│  Binaries:
│  Node: 22.14.0 - D:\Program Files\nodejs\node.EXE
│  npm: 10.9.2 - D:\Program Files\nodejs\npm.CMD <----- active
│  Browsers:
│  Chrome: 147.0.7727.56
│  Edge: Chromium (140.0.3485.54)
│  Firefox: 143.0 - C:\Program Files\Mozilla Firefox\firefox.exe
│  npmPackages:
│  @storybook/angular: 10.3.5 => 10.3.5
│  storybook: 10.3.5 => 10.3.5

Additional context

No response

[dosubot]

Hi @yuyu668668! I'm Dosu and I’m helping the storybook team.

The 404s you're seeing on sb-manager/ assets are because the manager bundle is not built with webpack — it's built with esbuild and served from hardcoded routes (/sb-manager/, /sb-addons/, etc.) [1]. Setting output.publicPath in webpackFinal only affects the preview iframe bundle, not the manager [2].

There is currently no built-in Storybook config option to change the base path for all assets [3]. The <base href> tag and webpackFinal publicPath won't reach the manager's JavaScript imports.

To serve Storybook under /storybook/, you'll need to handle it at the server level — e.g., a reverse proxy (nginx, Apache, etc.) that strips the /storybook/ prefix before forwarding requests to Storybook's dev server. For example in nginx:

location /storybook/ {
    proxy_pass http://localhost:4401/;
}

This way the Storybook dev server still sees requests at /, and your users access it at /storybook/.

If you're building for static deployment (not dev server), Storybook 10 with the Vite builder has improved relative path handling that may work better for subdirectory deployments [4], though Angular support for the Vite builder may vary.

Could you share more about your use case — is this for local development behind a proxy, or a static production deployment? That would help narrow down the best approach.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.