psychobolt

@krassowski Yeah it will be a issue for monorepo tools that don't support `portal:`. From my case, it works with my setup using [turbo](https://github.com/vercel/turbo).

I suppose you can manually reapply the patch after upgrade using `git apply` e.g. ```sh yarn patch @storybook/core@npm:8.3.5 ➤ YN0000: Package @storybook/core@npm:8.3.5 got extracted with success! ➤ YN0000: You can...

Can someone point out in the docs how I can disable all warnings?

> > Can someone point out in the docs how I can disable all warnings? > > You can use empty ouputs to disable the warning: > > ```json >...

I've found out in my case, I can suppress all warnings, including the main issue here. It's in the [environment variable docs](https://turbo.build/repo/docs/reference/system-environment-variables): https://github.com/vercel/turborepo/blob/bf8fa90dbb69a292ff7bb47f0836258ce9530e29/docs/repo-docs/reference/system-environment-variables.mdx#L21 e.g. `TURBO_GLOBAL_WARNING_DISABLED=1 yarn turbo run lint`

I concur that we need a optional flag for outputs. Sometimes there are parts of the task we want to run but don't output results.

I have same issue, csf needs to be upgraded. Adding this to my `package.json` for my `yarn` setup is a temporary workaround: ```json "resolutions": { "@storybook/[email protected]/@storybook/csf@npm:^0.1.2": "npm:0.1.9" } ```

Essentially broken for interpolated url strings in Sass in build mode. This was working in Vite 6 and broken in Vite 7. A small mixin utility which emit the file...

https://github.com/storybookjs/eslint-plugin-storybook/issues/209

For whatever reason, I ran into issue on github actions. Didn't know it will migrate cache from another drive: https://github.com/psychobolt/vite-storybook-boilerplate/actions/runs/8088993299/job/22104165674#step:4:104