Assorted link fixes

[XhmikosR]

There are plenty more redirected links, but I thought I'd make a first PR with these fixes. :)

I could probably squash the first and the third patch into one if you prefer.

PS1. I'd appreciate if someone could update the build assets for me before merging this. I thought this was automated and there are too many npm vulnerabilities AFAICT to even try to do npm i.
PS2. I'm not familiar with the commitlint conventions, so bear with me here
PS3. I personally prefer using Number.POSITIVE_INFINITY for concurrency, but I'm not 100% sure on which Node.js versions is supported. It doesn't change the functionality but it's more explicit.

[AppVeyorBot]

✅ Build karma 2969 completed (commit 48ad6b8d51 by @XhmikosR)

[karmarunnerbot]

✅ Build karma 571 completed (commit 48ad6b8d51 by @XhmikosR)

[karmarunnerbot]

✅ Build karma 572 completed (commit 48ad6b8d51 by @XhmikosR)

[devoto13]

1. It is automated, the generated website will be updated once the next release is published. So you don't need to worry about it.

2. You can do something like the below to make CI happy:

   docs: fix redirected npmjs links
   docs: change npm to lowercase
   docs: use https when possible

3. I would say, leave it be.

[XhmikosR]

Thanks for the hints! That being said, the changes don't affect only the docs. How can I combine more than one component? Maybe docs,core?

[devoto13]

AFAICT only comments are updated, so it should be fine with just docs. Or you can use “docs(core): message” if changes are specific to core.

[XhmikosR]

There's one link in code too but I don't think it matters a lot.

[AppVeyorBot]

✅ Build karma 2970 completed (commit e6eeb58478 by @XhmikosR)

[karmarunnerbot]

✅ Build karma 573 completed (commit e6eeb58478 by @XhmikosR)

[karmarunnerbot]

✅ Build karma 572 completed (commit e6eeb58478 by @XhmikosR)

[devoto13]

There's one link in code too but I don't think it matters a lot.

Yes.

PS I've amended the last commit to make CI happy. These were changes in the generated files coming from node_modules, so we can't change them to https here.

[karmarunnerbot]

✅ Build karma 574 completed (commit 9f4779f7ee by @XhmikosR)

[XhmikosR]

I'd like to keep those links, though. Can't you just update the dist files?

[AppVeyorBot]

✅ Build karma 2971 completed (commit 9f4779f7ee by @XhmikosR)

[karmarunnerbot]

✅ Build karma 573 completed (commit 9f4779f7ee by @XhmikosR)

[devoto13]

I'd like to keep those links, though. Can't you just update the dist files?

Unfortunately, we can't do it. Otherwise, we'll have to give up (unnecessarily complicate) a check that bundled client code is up-to-date, which is IMO more important than not having HTTP links.

The right fix would be to change the link in https://github.com/webmodules/dom-serialize, get a release, and update, but the package looks abandoned. Not sure if it is worth the trouble.

[XhmikosR]

Ah, OK, that makes sense. I wasn't aware that was 3rd-party code. All good then :)

[XhmikosR]

BTW the bots are too chatty 😛

[devoto13]

BTW the bots are too chatty 😛

You can block them to avoid any notifications. At least that's what I did 😄

[johnjbarton]

Thanks!

[karmarunnerbot]

🎉 This PR is included in version 6.3.3 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀