three-typescript-starter VS node-starter-kit

I'm trying to use TS to write a graphic application for class and importing my libraries is giving me hell. I'm using three-typescript-starter, which runs fine, but I want to go a bit further and substitute its three.js dependency with @types/three from DefinitelyTyped. I've installed it updating the dependencies body on package.json:

Here is link number 1 - Previous text "API"

I'm deploying by either manually by running yarn deploy script or firing it via GitHub Actions when a PR is created, updated, or merged to the main branch.

Example: github.com/kriasoft/node-starter-kit

Nope. Just plain GraphQL.js + Knex.js (example), often typed manually since it's not where most of the time spend on when building an API server (though it can be automated via a scaffolding script if there are too many db tables). Generating TypeScript definitions off the actual db schema using knex-types (example).

Examples: - https://github.com/kriasoft/node-starter-kit - basic Node.js API starter kit - https://github.com/kriasoft/graphql-starter - monorepo template with GraphQL, React, Relay

I can help you developing a (GraphQL API) server for your web and/or mobile app as well as CI/CD workflows, optimized for serverless infrastructure in Google Cloud Platform. The initial version (first iteration) will be ready and live in under three days! Code examples:

https://github.com/kriasoft/node-starter-kit

You may want to browse through https://github.com/kriasoft/node-starter-kit to pick up some common patterns (e.g. transactional emails, OAuth 2.0 authentication, user sessions, views, db migrations, etc.).