Issue with Table generation

POST /dev/auth/sign-up (λ: sign-up) One of the tables was not found, verify table exists before retrying. Error: Cannot do operations on a non-existent table

Run the create user curl and get the above

NB// Also add docs about setting up AWS credentials and the defaults needed perhaps

Hi, Serverless Framework maintainer here. I stumbled upon this repository and I'm wondering if Serverless Framework Compose could be useful here?

Furthermore we're exploring possible integrations with Learn/Nx/Turborepo, looking to bounce ideas about that. So I thought I'd open an issue ^^

Hello,

First off, as a long time Serverless Framework user, I love what has been done here!

So much so, I am planning on using this as a PoC at my job. I have 2 quick question before I do though:

1. Would I easily be able to integrate a React frontend into the repo? - I have looked over the Nx Documentation and believe it should be possible but I would like your opinion as you definitely have more experience in Nx than myself.

2. If a frontend service is possible, would you be able to share types across both?

Thanks, Connor

Dependency error occurred using npm 8.11.0, with npm 8.5.0 it installs everything fine

Steps to reproduce:

• Use npm version = 8.11.0

It got me this error over here:

While resolving: @nrwl/[email protected]
Found: @typescript-eslint/[email protected]
node_modules/@typescript-eslint/parser
  dev @typescript-eslint/parser@"5.19.0" from the root project
  peer @typescript-eslint/parser@"^5.0.0" from @typescript-eslint/[email protected]
  node_modules/@typescript-eslint/eslint-plugin
    dev @typescript-eslint/eslint-plugin@"5.19.0" from the root project

Could not resolve dependency:
peer @typescript-eslint/parser@"~5.18.0" from @nrwl/[email protected]
node_modules/@nrwl/eslint-plugin-nx
  dev @nrwl/eslint-plugin-nx@"14.1.2" from the root project

Conflicting peer dependency: @typescript-eslint/[email protected]
node_modules/@typescript-eslint/parser
  peer @typescript-eslint/parser@"~5.18.0" from @nrwl/[email protected]
  node_modules/@nrwl/eslint-plugin-nx
    dev @nrwl/eslint-plugin-nx@"14.1.2" from the root project

What we can do in this case?

Usually I would just start to bump versions from those dependencies. I'm new to open source projects and I would love to know what approach we use in these dependency error cases.

And I'm curious why this happens, all of the versions are set to the exact match in package.json

After clone I was running npm install and I got this error:

npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @nrwl/[email protected]
npm ERR! Found: @typescript-eslint/[email protected]
npm ERR! node_modules/@typescript-eslint/parser
npm ERR!   dev @typescript-eslint/parser@"5.19.0" from the root project
npm ERR!   peer @typescript-eslint/parser@"^5.0.0" from @typescript-eslint/[email protected]
npm ERR!   node_modules/@typescript-eslint/eslint-plugin
npm ERR!     dev @typescript-eslint/eslint-plugin@"5.19.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @typescript-eslint/parser@"~5.18.0" from @nrwl/[email protected]
npm ERR! node_modules/@nrwl/eslint-plugin-nx
npm ERR!   dev @nrwl/eslint-plugin-nx@"14.1.2" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: @typescript-eslint/[email protected]
npm ERR! node_modules/@typescript-eslint/parser
npm ERR!   peer @typescript-eslint/parser@"~5.18.0" from @nrwl/[email protected]
npm ERR!   node_modules/@nrwl/eslint-plugin-nx
npm ERR!     dev @nrwl/eslint-plugin-nx@"14.1.2" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Hi

Many thanks for putting this repo together, it is an excellent example.

What are your thoughts on using a Dependency Injection library like tsyringe? Could 'newing up' several dependencies in your todo service lead to a lot of boilerplate setup for each handler when more abstractions are created around IO and Business Logic?

I've forked your repo, created a branch and refactored the todo service with a few tests as a basic example - https://github.com/stottle-uk/nx-serverless/tree/dependency_injection.

Any thoughts or ideas you have would be much appreciated.

Kind regards