Add Deno shield

[rojvv]

No description provided.

[rojvv]

If its style not matching with the other badges is a problem, we can modify the styles of the shieldsio badges. The style of the Deno shield is not modifiable.

[KnorpelSenf]

Yes, please align the designs before we merge this.

[rojvv]

@KnorpelSenf How are they looking now?

[EdJoPaTo]

[KnorpelSenf]

LGTM. Thanks! Good idea :)

[KnorpelSenf]

In fact, img.shields.io allows us to use any logo, text, and design. If we want, we could switch back to the old designs, and simply avoid pulling in the Deno shield from deno.dev. What do you think?

[rojvv]

@KnorpelSenf If you prefer, we can remove the version part on the npm badge and do all of the work with shieldsio.

[KnorpelSenf]

I think it makes a lot of sense to have the same version on both shields. That way, it's very clear how we publish the identical versions for both runtimes.

[rojvv]

That way you should use the Deno shield. Because there won't be a way to add the version to a manually made shieldsio badge, and it won't look cool if we have the version on the npm badge, but not on the Deno one.

[KnorpelSenf]

Ah right, good point, I did not think about that. In that case, we can leave things as they are now.

[EdJoPaTo]

Alternatively… isnt shields.io open source? 😏

[KnorpelSenf]

You want to fork and add the feature we need?

[rojvv]

@EdJoPaTo Does that mean you will host your instance with this feature, or do you mean to PR this feature? They don’t accept PRs easily. Reference: badges/shields#7831

[KnorpelSenf]

It seems like there is progress on the linked PQ now.

[rojvv]

Yes, happily.

[KnorpelSenf]

@roj1512 this PQ modified the section controlled by all-contributors. The styling will be overwritten whenever a new contributor gets listed in the README.

Should we maybe switch to the automatically generated badge the is described in all-contributors/all-contributors#406?