Invalid type definitions - static import of ESM types from CJS types about functions HOT 5 OPEN

Thanks for reporting this! It's good to know there's a workaround, i'll add it to our internal triage.

from functions.

I'm a bit surprised about TypeScript emitting this error for a .d.ts file. That can't use require anyways, right?

from functions.

They're not using require, but you can only import CJS from ESM if you use a dynamic import. Another possible solution besides updating the types would be to distribute this package as ESM.

from functions.

They're not using require, but you can only import CJS from ESM if you use a dynamic import.

We're only importing @netlify/serverless-functions-api for types:

https://github.com/netlify/functions/blob/main/src/function/v2.ts#L1

So I don't think that an actual import line shows up in the generated JS file. This seems to be purely about the declaration file that TypeScript generates, and I would have expected TypeScript to generate it in a way that's compliant with CJS, because that's how it's configured:

Anyways, distributing this as ESM makes sense to me. @eduardoboucas do you see any reason why this might become a problem? Maybe consumption from within Next.js sites?

from functions.