Link to the code that reproduces this issue

https://github.com/robpc/nextjs-standalone-storybook-test

To Reproduce

Create the project

npx create-next-app@latest nextjs-standalone-storybook-test
cd nextjs-standalone-storybook-test/

Edit the next.config.js

/** @type {import('next').NextConfig} */
const nextConfig = {
    output: 'standalone'
}

module.exports = nextConfig

Test the standalone build

$ npm run build
# ...
$ du -sh .next/standalone/node_modules/
23M     .next/standalone/node_modules/

Add storybook

npx storybook@latest init

Retest the standalone build

$ npm run build
# ...
$ du -sh .next/standalone/node_modules/
145M    .next/standalone/node_modules/

Current vs. Expected behavior

Since storybook adds no dependencies used in app/, the expectation is that the output would be the same as the build without storybook. In other examples this was observed to be much larger (ex 400mb). This issue is similar to #51029

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP Fri Jan 27 02:56:13 UTC 2023
Binaries:
  Node: 18.16.0
  npm: 9.5.1
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.0.1
  eslint-config-next: 14.0.1
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.2.2
Next.js Config:
  output: standalone

Which area(s) are affected? (Select all that apply)

Standalone mode (output: "standalone")

Additional context

No response