Haven't plated with it, but it looks interesting. Not sure how far it will get used in practice or if/how any node support is... doesn't seem to have any.
Examples are fine... can post the dev.to articles if interresting/prudent as well (see about page on posting rules). TS is okay too. As are github links.
In general the only time I've blocked github or dev.to are specific users/accounts posting a lot of off-topic things... like Python apps in github.
Would suggest limiting non-major version update posts to about once a quarter... there isn't that much news flow here, so too many updates from a project like this will really stick out and start to turn people off.
I understand the desired effect, just pointing out that you may result in the opposite of what you're trying to accomplish.
Also, feel free to post interesting JS/TS finds you come across as well as your own work.
I don't change too much with my Biome config... I can say that when I first started, the config options were really hard to figure out without examples, but I think the documentation has expanded since then. I don't know about your specific case.
I would probably defer to typescript annotations if you want to start setting arguments as optional for a constructor or given methods. I will usually assign a manual default if I want typed behavior. But that will involve adding the TS compiler in addition to Biome, which only partially checks TS.
Carefull with things like Array.prototype.forEach with built-in functions. forEach passes a asecond argument for the position within the array, this can have unexpected consequences, such as if you're passing parseInt, or another function that optionally accepts a second parameter.
An anonymous lambda is often the best option.