feat: Implement useDateField with Temporals API

[logaretm]

This pull request introduces several significant changes to the i18n (internationalization) and calendar functionalities within the packages/core module. The most important changes include the addition of new dependencies, enhancements to locale handling, and the introduction of new calendar-related utilities.

Enhancements to locale handling:

• packages/core/src/i18n/getCalendar.ts: Added a new function getCalendar to retrieve the calendar identifier for a given locale.
• packages/core/src/i18n/getDirection.ts: Modified the getDirection function to accept an Intl.Locale object instead of a string.
• packages/core/src/i18n/getTimezone.ts: Added a new function getTimeZone to retrieve the timezone for a given locale.
• packages/core/src/i18n/getWeekInfo.ts: Added a new function getWeekInfo to retrieve week information for a given locale.
• packages/core/src/i18n/useLocale.ts: Enhanced the useLocale composable to support locale extensions and retrieve additional locale-related information.

Calendar-related utilities:

• packages/core/src/useCalendar/index.ts: Introduced new exports for calendar-related functionalities.
• packages/core/src/useCalendar/types.ts: Defined new types for calendar identifiers and calendar days.
• packages/core/src/useCalendar/useCalendar.ts: Implemented the useCalendar composable to manage calendar state and provide calendar-related data.
• packages/core/src/useCalendar/useCalendarCell.ts: Added the useCalendarCell composable and CalendarCell component for managing individual calendar cells.

New dependencies:

• packages/core/package.json: Added the @js-temporal/polyfill dependency to support temporal functionalities.

Additional changes:

• packages/core/src/constants/index.ts: Added new field type prefixes for DateTimeField and DateTimeSegment.
• packages/core/src/useDateTimeField/constants.ts: Introduced utility functions for handling date-time segments.
• packages/core/src/useDateTimeField/index.ts: Added exports for date-time field functionalities.
• packages/core/src/i18n/useDateFormatter/index.ts: Implemented the useDateFormatter composable to format dates using the temporal polyfill.
• packages/core/src/i18n/useNumberParser/index.ts: Enhanced the useNumberParser composable with additional functionality and type definitions. [1] [2] [3] [4] [5]

[changeset-bot]

⚠️ No Changeset found

Latest commit: 37c55d7

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

[logaretm]

Closing this in favor of #132

We will switch the implementation to use @internationalized/date instead. The 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.