storybook [Bug]: 在构建Next.js时,使用Nx时会收到信号SIGSEGV

whhtz7ly  于 2个月前  发布在  其他
关注(0)|答案(2)|浏览(32)

描述bug

嘿!
当我在自托管的Github action runner上运行Next.js与Nx的构建时,遇到了以下错误。

> nx run app:build:production

⚠ No build cache found. Please configure build caching for faster rebuilds. Read more: https://nextjs.org/docs/messages/no-cache
Attention: Next.js now collects completely anonymous telemetry regarding usage.
This information is used to shape Next.js' roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://nextjs.org/telemetry
  ▲ Next.js 14.2.4
  - Experiments (use with caution):
    · instrumentationHook
    · outputFileTracingRoot
   Skipping linting
   Checking validity of types ...
   Creating an optimized production build ...
Build process exited due to   signal SIGSEGV

问题出现在升级到"@storybook/nextjs": "8.0.8",以上版本后。
影响Next.js构建和构建Storybook。

复现链接

/

复现步骤

  • 无响应*

系统

Storybook Environment Info:
  System:
    OS: Linux 5.10 Alpine Linux
    CPU: (8) x64 AMD EPYC 7R32
    Shell: 1.35.0 - /bin/ash
  Binaries:
    Node: 20.2.0 - /usr/local/bin/node
    Yarn: 4.2.2 - /usr/local/bin/yarn <----- active
    npm: 9.6.6 - /usr/local/bin/npm
  npmPackages:
    @storybook/addon-a11y: ^8.1.8 => 8.1.8 
    @storybook/addon-designs: ^8.0.2 => 8.0.2 
    @storybook/addon-essentials: ^8.1.8 => 8.1.8 
    @storybook/addon-interactions: ^8.1.8 => 8.1.8 
    @storybook/addon-links: ^8.1.8 => 8.1.8 
    @storybook/addon-mdx-gfm: ^8.1.8 => 8.1.8 
    @storybook/addon-storysource: ^8.1.8 => 8.1.8 
    @storybook/addons: ^7.6.17 => 7.6.19 
    @storybook/api: ^7.6.17 => 7.6.19 
    @storybook/client-api: 7.6.17 => 7.6.17 
    @storybook/core-server: ^8.1.8 => 8.1.8 
    @storybook/manager-api: ^8.1.8 => 8.1.8 
    @storybook/nextjs: 8.1.8 => 8.1.8 
    @storybook/preview-api: ^8.1.8 => 8.1.8 
    @storybook/react: ^8.1.8 => 8.1.8 
    @storybook/source-loader: ^8.1.8 => 8.1.8 
    @storybook/test: ^8.1.8 => 8.1.8 
    @storybook/test-runner: ^0.18.2 => 0.18.2 
    eslint-plugin-storybook: ^0.8.0 => 0.8.0 
    msw-storybook-addon: 2.0.2 => 2.0.2 
    storybook: ^8.1.8 => 8.1.8 
    storybook-addon-pseudo-states: ^3.1.1 => 3.1.1 
    storybook-addon-rtl-direction: ^0.0.19 => 0.0.19 
    storybook-addon-swc: ^1.2.0 => 1.2.0

其他上下文

  • 无响应*
b1zrtrql

b1zrtrql1#

你好,感谢你报告这个问题。你有可以分享的可复现仓库吗?如果没有,你能通过$x_{1e0f1}^{x}$创建一个吗?我们优先处理有可复现性的bug报告。谢谢!

k5ifujac

k5ifujac2#

你好,很遗憾现在不是这个时刻。
我们的仓库太大了,无法"清理"成为一个可复制的项目,而且创建一个新的项目也有些困难,因为这是一个简单的项目,没有使用nx和storybook组合。
它在"@storybook/nextjs": "8.0.8"版本之后开始出现问题,所以8.0.8仍然可以工作(这就是我们现在拥有的),但更新后的版本正在出现问题。
奇怪的是,错误报告是关于next.js构建因为更新而出现问题,而不仅仅是storybook构建。
有什么建议吗?很可能问题出在我们这边。🤔

相关问题