staticDirs are not copied in the same destination depending on the build target

[JeanRemiDelteil]

Please provide the environment you discovered this bug in.

In an Angular repository, and following your documentation, add configuration for:

• @analogjs/storybook-angular:start-storybook
• @analogjs/storybook-angular:build-storybook

Import some fonts in your project, as static assets with staticDirs.

Which area/package is the issue in?

storybook-angular

Description

When using @analogjs/storybook-angular:start-storybook
This staticDirs config is necessary:

  staticDirs: [
    { from: '../fontface/fonts', to: 'fonts' },
  ],

When using @analogjs/storybook-angular:build-storybook
This staticDirs config is necessary:

  staticDirs: [
    { from: '../fontface/fonts', to: 'assets/fonts' }, // <-- we need to add "assets/" !!
  ],

Please provide the exception or error you saw

We should be able to see the same config in both build target.

Other information

No response

I would be willing to submit a PR to fix this issue

• Yes
• No

[brandonroberts]

I tested against this repo with the same configuration and couldn't reproduce the issue.

https://github.com/brandonroberts/angular-vite-storybook

We're using the same builders that Storybook uses underneath.

[JeanRemiDelteil]

@brandonroberts I managed to trim down to a small (if not minimal) reproduction repository. You should have received an invitation to see it.

The issue is probably caused by the folder hierarchy: Storybook is living as a sibling of the other Angular projects.
Though that did not caused any issues with the other builder.

On another note, I indeed saw that the package is calling the Storybook builders. It's too bad that it causes webpack to still be installed (but not used I suppose ?).

[brandonroberts]

That's correct. Installed but not used. We're re-using the @storybook/angular package which is a common pattern and didn't want to lost bug fixes and updates to Storybook. Will take a look at the repo and see

[brandonroberts]

I've dug into this and it looks like a bug on the Storybook side. I suggest filing an issue there with the reproduction. Converting to a discussion as there's a workaround.