Jon Ursenbach

I don't use NestJS so I'm not sure how to solve this. Do you know why it's trying to use the TS file directly instead of compiling it into your...

For what it's worth, if you're generating a JS SDK `api` will still generate TS types for you to use in local development. You don't need to generate a TS...

Besides @Cmoen11, is everyone else in this thread using Yarn?

@yangricardo That `prepareParams` file uses `fs` in order to handle file uploads through SDKs. If you're just using this in the browser you should be able to safely polyfill `fs`...

@afreemanio Would you be willing to share a working broken example of this in an isolated repository that I can play around with? Would be immensely helpful in figuring out...

I've not been able to replicate this, and we've not gotten any other reports about it, so I'm closing it out.

I don't want to speak for @kanadgupta here but I'm leaning towards not pulling this in. This kind of upload flow is something we've been tossing around over the past...

@garrett-wade No timelines as we're still formulating a plan for how it'll work, but we'd love to do it this year.

Seeing this as well with a simpler TS config. > File '/Users/erunion/code/node_modules/jest-extended/types/index.d.ts' is not a module.ts(2306) ``` import { toContainKey } from 'jest-extended'; expect.extend({ toContainKey }); ``` `__tests__/tsconfig.json`: ``` {...

This patch fixed this issue for our use-case of using `@tsconfig/node16` with `module: node16` and `moduleResolution: node16`: ```diff --- ./node_modules/ts-jest/dist/legacy/compiler/ts-compiler.js 2023-11-01 13:05:20.000000000 -0700 +++ ./node_modules/ts-jest/dist/legacy/compiler/ts-compiler.fixed.js 2023-11-01 13:09:38.000000000 -0700 @@ -132,7...