#473 · closed · 1 comments
This option is needed to solve https://github.com/grpc/grpc-node/issues/2617 which prevents grpc-js from being compiled using rollup-plugin-typescript2 Currently only ES2015, ES2020, ES2022 and ESNext module options are supported. Option was added in [Typescript 5.4](https://devblogs.microsoft.com/typescript/announcing-typescript-5-4/#support-for-require-calls-in---moduleresolution-bundler-and---module-preserve)
Apologies for the delayed response. > Option was added in [Typescript 5.4](https://devblogs.microsoft.com/typescript/announcing-typescript-5-4/#support-for-require-calls-in---moduleresolution-bundler-and---module-preserve) Per the [TSConfig Reference doc](https://www.typescriptlang.org/tsconfig/#preserve), this seems to be intended for mixed ESM/CJS imports/exports. However, Rollup only supports ESM input, so such mixed output wouldn't be compatible with Rollup. > This option is needed to solve [grpc/grpc-node#2617](https://github.com/grpc/grpc-node/issues/2617) which prevents grpc-js from being compiled using rollup-plugin-typescript2 Are you a maintainer there? I didn't see your handle in that issue thread nor in [a repo search](https://github.com/grpc/grpc-node/issues?q=commenter%3AExidex). Reading that issue, it doesn't seem clear to me why this option would be _required_ to resolve that issue. There seem to be other ways of resolving it and this doesn't seem to be the root cause. Similarly, Rollup's ESM limitation, as per above, make this suggestion a quite confusing way of attempting to work around that.