All the warnings are either "fire once" or "unlimited" based on the flag passed to last "create" method

[IMalyugin]

Basically, due to this piece of code:

process-warning/index.js

Line 94 in c0649f8

Object.assign(opts, { unlimited })

The last created warning decides wether all the created warnings are limited or unlimited. Thus in fastify, since last created warning is made unlimited:
https://github.com/fastify/fastify/blob/99a405a4e347629595ac5062c74d91675b1b34e5/lib/warnings.js#L58

warning.create('FastifyWarning', 'FSTWRN002', 'The %s plugin being registered mixes async and callback styles, which will result in an error in `fastify@5`', { unlimited: true })

All the declared warnings are spamming the application :)

Should either move opts inside "create" or add a new hashmap for the unlimited flag

[Uzlopak]

Yes, makes sense.

[Uzlopak]

@jsumners

[jsumners]

I saw this in the code a couple weeks ago. It wasn't clear to me if it would show as an issue or not. But clearly it does. A PR should be created that does not overwrite the global options with each new warning.