Roadmap to V5?

[H4ad]

This is the milestone for being able to update this library to V5.

Goals:

• Split each handler, adapter and framework into its own package.
• Be more independent from NodeJS, so you can easily migrate from NodeJS to Deno or another type of environment such as Bun or Cloudflare Workers.

About dividing the library into several packages, we will have:

• @h4ad/serverless-adapter: The core library which contains all contracts and core functionality.
• @h4ad/serverless-adapter-aws: Contains all AWS Adapters and Handler.
• @h4ad/serverless-adapter-azure: Which contains all Azure adapters and handler.
• @h4ad/serverless-adapter-firebase: Contains all Firebase Adapters and Handlers.
• @h4ad/serverless-adapter-huawei: Contains all Huawei adapters and handlers.
• @h4ad/serverless-adapter-gcp: Contains all GCP adapters and handlers.
• @h4ad/serverless-adapter-digital-ocean: Contains all Digital Ocean Adapters and Handlers.
• @h4ad/serverless-adapter-express: Contains the express framework.
• @h4ad/serverless-adapter-deepkit: Contains the deepkit framework.
• @h4ad/serverless-adapter-fastify: Contains the fastify framework.
• @h4ad/serverless-adapter-hapi: Contains the hapi framework.
• @h4ad/serverless-adapter-koa: Contains the koa framework.
• @h4ad/serverless-adapter-apollo-server: Contains the apollo-server framework.
• @h4ad/serverless-adapter-nodejs: Contains the network code related to Request and Response for NodeJS
• @h4ad/serverless-adapter-fetch: Contains the network code related to Request and Response for Fetch Spec, that can be used inside Cloudflare Workers and other kind of workers.

Things to consider:

• Should I use the monorepo approach?
  • If I use this scheme I must have multiple packages with different typescript versions and different nodejs versions.
• Should I create an organization instead of leaving it inside my nickname?