dotansimha / dotansimha/graphql-code-generator
`SIGSEGV` on `next@13.2.4` with `@graphql-codegen/client-preset-swc-plugin@0.1.2`
- Dominant language
- TypeScript
- Stars
- 11.3k
- Forks
- 1.4k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 23
Description
### Which packages are impacted by your issue?
`@graphql-codegen/client-preset-swc-plugin`
### Describe the bug
`next build` is running into a `SIGSEGV` for both`swc-plugin-graphql-codegen-client-preset-optimizer-test` and `@graphql-codegen/client-preset-swc-plugin@0.1.2` when upgrading to `next@13.2.4`. `13.2.3` was fine.
_See also this thread here: https://github.com/dotansimha/graphql-code-generator/issues/9057#issuecomment-1463568497_
_See also the vercel issue here: https://github.com/vercel/next.js/issues/46989_
### Steps to Reproduce the Bug or Issue
- Install next 13.2.4
- Add @graphql-codegen/client-preset-swc-plugin@0.1.2
- 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
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.