Description
To prepare for v5 we need to go through the list of repositories in this issue and:
- Determine if the module/project should be archived and marked as deprecated. Mostly we should look at the commit history to determine if the community is interested in the module/project. A secondary check would be inspecting the data for the module at npm-stat.com. Unless we have people using, and contributing to modules, we should be reducing our maintenance burden by archiving them.
- Evaluate if the module/project needs any updates. Most likely this will simply mean updating dependencies, dropping Node <= 16, and updating CI configuration accordingly (see footnote 1).
Note: we must pinBlue Oak is now OSI approved (https://opensource.org/license/blue-oak-model-license/), thus solving the licensing issue on this dependency.tap@16.3.9for any projects utilizing it. See Update modules for v5 #5116 (comment) for a required change related to this.
If you are interested in helping with any of these, please create a new issue in the repo you're interested in that has the title "Updating for v5" and a body with something like "👋 I'm X, and would like to work on this." It should also include a link back to this issue. After that issue is created, a member of the Fastify team will create a next branch for you to target. Once that branch is created, you will be able to start a new Pull Request that targets it. We will help out with any questions you may have.
-
.github - accept-negotiator
-
action-pr-title - ajv-compiler
- any-schema-you-like
- avvio
- aws-lambda-fastify
-
benchmarks - busboy
- compile-schemas-to-typescript
- create-fastify
- csrf
- csrf-protection
- deepmerge
-
deprecate-modules -
docs-chinese -
docs-korean -
docs-portuguese - env-schema
-
example - fast-content-type-parse (@nrayburn-tech)
- fast-json-stringify
- fast-json-stringify-compiler
-
fast-proxy - fast-uri
- fastify
- fastify-accepts
- fastify-accepts-serializer
- fastify-api
- fastify-auth
- fastify-autoload
- fastify-awilix
- fastify-basic-auth
- fastify-bearer-auth
- fastify-caching
- fastify-circuit-breaker
- fastify-citgm
- fastify-cli
- fastify-compress
- fastify-cookie
- fastify-cors
- fastify-diagnostics-channel
-
fastify-dx -
fastify-early-hints - fastify-elasticsearch
- fastify-env
- fastify-error
- fastify-etag
-
fastify-example-todo -
fastify-example-twitter - fastify-express
- fastify-flash
- fastify-formbody
- fastify-funky
- fastify-helmet
- fastify-hotwire
- fastify-http-proxy
- fastify-jwt
- fastify-kafka
- fastify-leveldb
- fastify-mongodb
- fastify-multipart
- fastify-mysql
- fastify-nextjs
- fastify-oauth2
- fastify-passport
- fastify-plugin
- fastify-postgres
- fastify-rate-limit (@Eliphaz-Bouye)
- fastify-redis
- fastify-reply-from
- fastify-request-context
- fastify-response-validation
- fastify-routes
- fastify-routes-stats
- fastify-schedule
- fastify-secure-session
- fastify-sensible
-
fastify-snippet -
fastify-soap-client -
fastify-starter-codesandbox - fastify-static
- fastify-swagger
- fastify-swagger-ui
-
fastify-test - fastify-throttle
-
fastify-type-provider-fluent-json-schema - fastify-type-provider-json-schema-to-ts
- fastify-type-provider-typebox
-
fastify-typescript-extended-sample - fastify-url-data
- fastify-vite
- fastify-websocket
- fastify-zipkin
- fluent-json-schema
- forwarded (@Gesma94)
-
gh-issues-finder -
github-action-merge-dependabot -
graphics -
help - json-schema-ref-resolver
- light-my-request
- manifetch
- middie
- one-line-logger
- pacchetto
- point-of-view
- pre-commit
- process-warning
- proxy-addr
-
releasify - restartable
- safe-regex2
- secure-json-parse
-
semver-major-release-script - send
- session
- skeleton
-
tsconfig - under-pressure
-
vite-plugin-blueprint -
website - workflows (@nrayburn-tech)
Footnote 1
Regarding updating the CI configuration in these projects. Most projects in the list should have a CI workflow that looks like https://github.com/fastify/fast-content-type-parse/blob/4de4e57f2d2c2893094c2a46069e04767b179d8e/.github/workflows/ci.yml#L1-L23. Thus, we have a few possible changes:
- If a project has a different configuration that the one linked in the previous paragraph, it is likely that the configuration should be update to match it.
- If the project is using the linked configuration, it should be updated to reference the
v4tag of the worklows repo once issue Create a v4 set workflows#106 has been resolved. - If it is determined that the shared configuration should not be used for the project, the configuration should be updated as outlined at the top of this issue.