Aarne Laur

get the /home/runner/.npm/_logs/* from actions and things will get more transparent i hope. Add something like this as the last step in your action. ``` - name: Store error logs...

https://github.com/semantic-release/npm/pull/512#issuecomment-1245406224

The problem is with npm starting from version 8.5 that comes by default with node 16.15. Adding `workspaces-update = false` to your `.npmrc` will fix the issue on newer npm...

Temporary workaround for anyone hitting the same issue would be to run `npx @magic-works/ts-esm-migrate ./src/generated` after generation

What about interfaces do they share the same faith?

The problem is with npm starting from version 8.5 that comes by default with node 16.15. Adding `workspaces-update = false` to your `.npmrc` will fix the issue on newer npm...

We can also think of `bring your own jwt library` type of integrations mby?

The only 2 exposed part of `jsonwebtoken`/`jwk` is `VerifyOptions` and `JwksClient.Options` interfaces, as defined below ``` typescript interface VerifyOptions { algorithms?: Algorithm[] | undefined; audience?: string | RegExp | Array...

... looking at the code only and ignoring the migration effort, it might be better to break the compatibility :( ```typescript type JwtPluginOptions = { tokenLookupLocations: AtleastOneItem; tokenVerificationFunction: (token:string) =>...

Example implementation https://github.com/aarne/graphql-yoga/tree/feat_jwt_external/packages/plugins/jwt/src ... keeps plugin clean and moves all [jsonwebtoken related functions to separate file](https://github.com/aarne/graphql-yoga/blob/feat_jwt_external/packages/plugins/jwt/src/jsonwebtoken.ts). Im not sure what is the best distribution model ... separate package or separate...