2022-05-07 remaining work:

The following list is hoisted from comment #3733 (comment)

• aws-lambda-fastify
  • Rename package (Rename Module aws-lambda-fastify#110)
• fastify-auth
  • Update dependencies (Updated to Fastify v4 fastify-auth#154)
• fastify-awilix
  • Update dependencies (Updated to Fastify v4 fastify-awilix#73)
• fastify-csrf
  • Rename package
• fastify-flash
  • Update dependencies
• fastify-schedule
  • Update dependencies (Updated to Fastify v4 fastify-schedule#82)
• fastify-session
  • Missing release notes
  • Update dependencies
• fastify-swagger
  • Update dependencies
• middie
  • Rename package (Rename module middie#148)
• point-of-view
  • Rename package (Rename module point-of-view#325)
• under-pressure
  • Rename package (Rename module under-pressure#166)
• any-schema-you-like
  • Rename package (Rename module any-schema-you-like#25)

Original post:

Issue

If we are going to deprecate fastify-* modules, as outlined in #3482 (comment), then I really need help with https://github.com/fastify/deprecate-modules.

To start, I need help auditing https://github.com/fastify/deprecate-modules/blob/a7a87b05d129e04d7e36bd4f0eb07d479e2d7b6f/lib/modules.json to determine:

1. Is the list of modules correct
2. Are the versions correct? versionToPublish will be the new fastify-* version for the module. The newModule.version will be the version published under @fastify/*.

Subsequent to that, I need help with the todo list in the readme. In particular, is there anything that needs to be done for TypeScript in the deprecated modules (look at the templates)? How should the templates be updated for ESM exports?

Once we have the deprecation portions written and tested, we need to work on adding script for:

1. Updating GitHub repository information (rename the repo, update links in package.json, etc)
2. Patching the package.json with the new name and version for the new @fastify/* packages

attn: @fastify/core