James Sumners

I assert that the `fastify` instance is very similar to an IoC container.

> > Note: we must pin [email protected] for any projects utilizing it. > > Should we pin specifically to `[email protected]` or is `^16` sufficient? `16.3.9` is the last release in...

I am keeping up with that thread (as you probably can see). I will update the task list here if it comes about in time that Blue Oak is authorized....

There is not yet a resolution on the OSI inclusion of Blue Oak.

> fastify-dx is archived, it can be marked as done @galvez please mark `fastify-dx` as deprecated on npmjs.com.

Blue Oak is now OSI approved. We should be able to utilize `tap@18` without issue at this point (unless @mcollina says we need even further approval from OpenJSF)`. https://opensource.org/license/blue-oak-model-license/

It is approved. My updates above are accurate. https://github.com/openjs-foundation/cross-project-council/pull/1245

Yes, that is an accurate summation. Regarding dependencies, please update to the latest major versions unless there is some reason to prevent it (e.g. the module changed to ESM only).

That is complicated. `tap@16` isn't going to give us full coverage checking on Node 20+, but current `tap` is a very heavy dependency. Switching to `node:test` has other issues. I...

> Not sure if @fastify/core would like to change the default logger since it is customizable already + https://github.com/fastify/fastify/issues/2841#issuecomment-775779962 + https://github.com/fastify/fastify/issues/1268