add support for fastify@4
See original GitHub issueCurrently fastify v4 has RC pre-releases. Our TAV tests and supported-technologies doc page say we support fastify >=1
. We should change that to be specific about the major versions support, and we should test and update for fastify v4 as necessary.
Issue Analytics
- State:
- Created a year ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Plugins - Fastify
Plugins. Fastify allows the user to extend its functionalities with plugins. A plugin can be a set of routes, a server decorator, or...
Read more >Updating your Node apps for Fastify 4 - Glitch Help Center
Update Fastify. In the package.json ADD PACKAGE dropdown, select the updated version of the Fastify package (it should be 4+).
Read more >Facing unexpected tokken '?' error in fastify 4 - node.js
As wrote in the Fastify LTS statement, fastify v4 support Node.js >= 14. That said, the fastify codebase uses nullish operator ?? and...
Read more >Announcing Fastify v4 release candidate! - Medium
We now support only Node.js v14+, and have fixed some bugs which ... URL decoding https://github.com/delvedor/find-my-way/pull/207; Added ...
Read more >fastify-metrics - npm
This plugin also adds two http metrics for your routes: ... x.x - supports fastify-4.x prom-client-14.x ... Support disabling metrics in route config....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
fastify@4 requires node >=14.6.0 – because it uses pino@8 which uses on-exit-leak-free@1 which requires https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/FinalizationRegistry which came in node 14.6.0.
@karliell
When I run this:
I see that FSTDEP011 warning:
However, when I run this:
I do not see that deprecation warning. I get the same behaviour whether or not the
elastic-apm-node
APM agent is being used.Do you see different behaviour? I’m using fastify@4.9.2 and elastic-apm-node@3.40.1.