Christoph Pflüger

> > This causes useSession's useEffect to execute two requests instead of one. > > Can you describe the issue this is causing you? I noticed it as I was...

> Can I gently nudge this pull request? I hope if gets merged already as this is also a blocker in our application - I think this should be considered...

> Thanks for the PR @git-chrisp and sorry for the delayed response, I reviewed your PR It seems like the added method `updateSession` is exactly the same as `getSession`, the...

- I am using TypeScript. Hence, I have a serverless.ts. - I would like to import my lambda functions in said serverless.ts. - As said serverless.ts has to use `module.exports,`...

> @git-chrisp got it, so to sum it up: > > You would like to use `export` instead of `module.exports` in `serverless.js`/`serverless.ts` configuration, is that correct? Correct.

Here is what I have so far: https://github.com/git-chrisp/serverless 1. I am now making use of `importModule` in `read.ts` 2. Created a fixture to test TypeScript files and ESM support I...

@pgrzesik The issue with the current test for a `serverless.ts` is, that it doesn't really test for actual TypeScript support. It tests whether a file named `serverless.ts` can be used,...

@pgrzesik As we need to use `export default` to test the ESM support (which is not supported in the CommonJS environment the tests are executed), I suppose, the best way...

> Hey @zirkelc - thanks for reporting. I believe it would be possible and @git-chrisp was working on it for a while, but I'm not sure if that's still a...

@zirkelc Updating AWS Lambda functions to use NodeJS 16.x features should not be an issue. Using ES Modules with e.g. serverless-esbuild is already working. The issue is the configuration file...