Add fetchpriority prop

[codejet]

What:

Adding the currently still non-standard fetchpriority prop.

Why:

Priority hints are currently an unoffical W3C draft driven by Google (https://wicg.github.io/priority-hints/) but already supported in some Chromium-based browsers (https://caniuse.com/?search=fetchpriority). See also this article: https://web.dev/priority-hints/.

How:

Simply added the prop to packages/is-prop-valid/src/props.js, for now under the "Non-standard Properties".

Checklist:

• [N/A] Documentation
• [N/A] Tests
• Code complete
• [N/A] Changeset

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4151544

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 4151544:

Sandbox	Source
Emotion	Configuration

[codejet]

Hi, is there any interest in this? Otherwise I will close it. No hard feelings.

[oskareke]

This is an important SEO feature - could we please get this merged?

[DustinBrett]

@codejet

Hi, is there any interest in this? Otherwise I will close it. No hard feelings.

I see that Styled Components uses @emotion/is-prop-valid to decide if it will show a warning message. I see fetchpriority is considered valid now on https://validator.w3.org/ so I am wondering if we could reopen this PR?

[codejet]

@DustinBrett are you a maintainer here? otherwise: as last time there wasn't even a comment, i'm afraid it would be pointless to reopen it.

[DustinBrett]

Ah darn, well maybe one day it will get added. I might make a PR but who knows what will come of it.

[DustinBrett]

@DustinBrett are you a maintainer here? otherwise: as last time there wasn't even a comment, i'm afraid it would be pointless to reopen it.

It finally happened! #3093
FYI @codejet

[codejet]

Thanks @DustinBrett ✌️

I would have never thought that a PR can take 2.5 years 😅

[Andarist]

I would have never thought I'd maintain OSS projects instead of playing video games after days of full-time work and taking care of my family and kids... but hey, here we are 😉

This slipped through the cracks in the sea of notifications I get, sorry about that.

[codejet]

I totally get that @Andarist. I'm grateful to anyone maintaining OSS! I was still surprised to see this change merged 2+ years after I closed my original PR 😉