feat: Implement useDateField with @internationalized/date

[logaretm]

What

Swaps out the temporal implementation in #115 for @internationalized/date.

Why

While I loved working with temporals, the fact that they are not widely supported yet is not encouraging. I would have proceeded with them if they were at least Baseline supported.

My main reasons are:

• Existing polyfill sizes are too much to justify the investment
  • @js-temporal/polyfill is 56.7kb gzipped.
  • temporal-polyfill is 20.5kb gzipped.
  • @internationalized/date is 10.9kb gzipped.
• The question of what value type to use is muddied further.
  • Temporals while are great in serializing values, they cannot be used anywhere else. They need to be supported in Node.js and to be more common in the ecosystem as a whole.
  • Temporals won't probably be used by any developer today, so we are asking them to add a huge bundle size for little reason, especially those who are not interested in our i18n offering.
  • @internationalized/date is a little more common in the ecosystem and has utility outside formwerk use.

I think once temporals hit baseline, we will make that switch, its such a shame because it is a great API imo. Another alternative, is we find or fork or build a minimal version of the temporal spec and use it internally.

[changeset-bot]

🦋 Changeset detected

Latest commit: 379b5cf

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

This PR includes changesets to release 1 package

Name	Type
@formwerk/core	Minor

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

[pkg-pr-new]

Open in Stackblitz

npm i https://pkg.pr.new/formwerkjs/formwerk/@formwerk/core@132

commit: f68dacb