Bump preact from 10.5.13 to 10.5.14

[dependabot]

Bumps preact from 10.5.13 to 10.5.14.

Release notes

Sourced from preact's releases.

10.5.14

Features

• Compat: Add flushSync (#3094, thanks @​zephraph)

Bug Fixes

• Prevent eager child removal (#3210, thanks @​JoviDeCroock)
• Compat: Update Fake React Version (#3189, thanks @​tim-on-github)
• Fix react-spring error caused by augmented function contexts (#3165, thanks @​developit)
• Use Array.prototype.slice.call for children arguments (#3143, thanks @​fzzle)
• Improve performance of vnodeId generation (#2978, thanks @​developit)
• Fix: should override children if null is provided as an argument (#3091, thanks @​clyfish)

Size

• refactor(diff-index): reuse i to reduce size (-32b) (#3193, thanks @​liuarui)
• Simplify unmount logic (#3120, thanks @​andrewiggins)

Typings

• Fix type definitions (#3191, thanks @​craftedsystems)
• Fix undefined initializer case for useState type (#3185, thanks @​rschristian)
• Make typings deno compatible (#3079, thanks @​lucacasonato)
• Change typing of event.this to be never (#3147, thanks @​JoviDeCroock)
• Update signature of lazy to reflect behavior (#3139, thanks @​JonasKruckenberg)
• Improve typing of forwardRef (#3144, thanks @​cmlenz)
• Fix the useRef typing to include undefined when called without initial value (#3056, thanks @​cmlenz)

Maintenance

• Docs: Removing suggestion to install Preact CLI (#3204, thanks @​rschristian)
• Upgrade karma-esbuild to support M1 chips (#3153, thanks @​marvinhagemeister)
• Rely directly on performance.now (#3130, thanks @​developit)
• Add The Guardian as a Github backer (#3086, thanks @​mchv)
• Fix typo in issue template (#3067, thanks @​rschristian)

Commits

• ba8353c Merge pull request #3212 from preactjs/10.5.14
• 145f167 10.5.14
• 55ee4bc (fix) - prevent eager child removal (#3210)
• c52de5c Merge pull request #3204 from preactjs/docs/readme-cli
• 2937892 docs: Removing suggestion to install Preact CLI
• 840095d refactor(diff-index): reuse i to reduce size (#3193)
• 1f89e50 Merge pull request #3191 from craftedsystems/fix/type-definition
• 9fc9de2 Add valid value options
• 51d607c Add attribute definition autoCapitalize to HTMLAttributes
• 50b90f8 Add attribute definition spellCheck to HTMLAttributes
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[robertknight]

The type of useRef changed so that if initialized with a value of type T|null then the returned ref's .current property now has type T|null instead of T.

Preact <= 10.5.13:

foo = useRef(/** @type {HTMLInputElement|null} */ (null));
foo.current // HTMLInputElement

Preact 10.5.14:

foo = useRef(/** @type {HTMLInputElement|null} */ (null));
foo.current // HTMLInputElement|null

The new behavior is technically more correct, but we've written code in various components which assumes the old behavior. In particular the new behavior is quite annoying for the common use case of a DOM ref which starts out as null and transitions to non-null after the first render. I think we should first check upstream that this was definitely an intentional decision, as it deviates from useRef's type definition in React.

[robertknight]

Related upstream PR - preactjs/preact#3222. TBC whether that resolves this issue.

[dependabot]

Superseded by #3845.