Fix missing GitHub Sponsor for npm fund

[ybiquitous]

We forgot to add our GitHub Sponsor to package.json (funding) when we started it.

$ npm fund stylelint
1: opencollective funding available at the following URL: https://opencollective.com/stylelint
2: github funding available at the following URL: https://github.com/sponsors/stylelint
Run `npm fund [<package-spec>] --which=1`, for example, to open the first funding URL listed in that package

In addition, this improves the financial section in the contribution guide:

• Add GitHub Sponsor
• Simplify links to Open Collective, including unsupported #backer or #sponsor

Which issue, if any, is this issue related to?

None.

Is there anything in the PR that needs further explanation?

I've also added a changelog item so that users can notice this npm fund change, but I can remove it if anyone don't consider it appropriate in the changelog.

[changeset-bot]

🦋 Changeset detected

Latest commit: b887263

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
stylelint	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[ybiquitous]

[out of topic] I'd like to apply these funding settings to other packages in https://github.com/stylelint, such as stylelint-config-recommended. If anyone knows how to achieve this easily, please let us know. 🙏🏼

Ref https://github.com/search?q=org%3Astylelint+funding+path%3Apackage.json&type=code

[romainmenke]

LGTM!

Thank you for this

[romainmenke]

I'd like to apply these funding settings to other packages in https://github.com/stylelint, such as stylelint-config-recommended. If anyone knows how to achieve this easily, please let us know.

We always need to add the exact same snippet in each package.json of a published npm package, right?

Edit:

Maybe doing all the releases to have this information publicly available is most of the work?

[ybiquitous]

@romainmenke Thanks for the quick review. 😄

We always need to add the exact same snippet in each package.json of a published npm package, right?

Exactly. I think it's better for all published packages in @stylelint to have the same funding field in their package.json. But, this is a tedious task, although it's rarely changed. 😅

EDIT: And, yes. We have to publish packages with their updated funding.

[ybiquitous]

[note] This snippet automatically updates the funding field in package.json:

#!/usr/bin/env node --experimental-default-type=module
import { execSync } from "child_process";

const funding = JSON.parse(
  execSync('npm view "stylelint" "funding" --json').toString(),
);

execSync('npm pkg delete "funding"', { stdio: "inherit" });

funding.forEach(({ type, url }, i) => {
  execSync(
    `npm pkg set "funding[${i}].type=${type}" "funding[${i}].url=${url}"`,
    { stdio: "inherit" },
  );
});

console.log('Updated package.json');