SIGSEGV on [email protected] with @graphql-codegen/[email protected]

[aplr]

Which packages are impacted by your issue?

@graphql-codegen/client-preset-swc-plugin

Describe the bug

next build is running into a SIGSEGV for bothswc-plugin-graphql-codegen-client-preset-optimizer-test and @graphql-codegen/[email protected] when upgrading to [email protected]. 13.2.3 was fine.

See also this thread here: #9057 (comment)

See also the vercel issue here: vercel/next.js#46989

Steps to Reproduce the Bug or Issue

• Install next 13.2.4
• Add @graphql-codegen/[email protected]
• Run next build
• SIGSEGV

Expected behavior

No segfault

Platform

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 22.3.0: Mon Jan 30 20:38:37 PST 2023; root:xnu-8792.81.3~2/RELEASE_ARM64_T6000
Binaries:
  Node: 18.13.0
  npm: 8.19.3
  Yarn: 1.22.19
  pnpm: 7.26.0
Relevant packages:
  next: 13.2.4
  eslint-config-next: 13.2.4
  react: 18.2.0
  react-dom: 18.2.0
  @graphql-codegen/client-preset-swc-plugin: 0.1.2

[aplr]

@graphql-codegen/client-preset-swc-plugin doesn't seem to be the only one, seems to have sth. to do with next's update of rust_toolchain probably?

See vercel/next.js#46989 (comment)

This is the PR causing issues for the other plugin, the update of rust_toolchain looks sus: https://github.com/vercel/next.js/pull/46971/files

[tyteen4a03]

We're running into the same issue on our Ubuntu docker build.

[YassinEldeeb]

Hey, thanks for reporting! We are currently tracking the issue with SWC maintainers to figure out a solution.

Please add a 👍 to the issue and feel free to join the conversation.
swc-project/swc#8315

I'll keep you updated!