Native Date vs External Parser: Which Approach Provides Consistent Time‑Zone Validation in VeeValidate?

The goal is to validate a user‑entered date string in a Vue 3 form such that the result is identical regardless of the client’s local time zone. VeeValidate’s built‑in date rule parses the value with the JavaScript Date constructor, which interprets strings without an explicit offset in the host environment’s zone. Two documented strategies exist to mitigate this:

• Pre‑process with a time‑zone library – e.g., date-fns-tz or moment-timezone – to convert the input to a UTC timestamp or an ISO string that includes an offset before passing it to the rule.
• Use a custom date_format rule – embed a parser that extracts any provided offset, normalises the value to UTC, and then performs the validation, keeping the logic declarative within the form schema.

Both approaches are documented, yet neither offers a built‑in flag to enforce a specific regional zone within the rule itself. The unresolved decision is whether to add an external dependency for zone handling or to rely on a custom rule that keeps the validation declarative but may increase complexity.

What are the trade‑offs in bundle size and maintainability when choosing date-fns-tz versus a custom date_format parser for time‑zone‑aware validation?

How does each approach affect server‑side validation consistency when the same form data is re‑validated in a backend environment that may run in a different time zone?