Invalid date in safari

Taming timezone tyrants

Timezones are pesky goblins. To get rid of them, end your datetime string with Z for UTC:

// Right: Safely in UTC
const dateUTC = new Date('2023-01-02T12:34:56Z');


Preserving sanity in cross-browser chaos

Using Regex: Swinging the all-purpose magic wand

Use regex to rescue dates in unrecognizable attire:

const hyphensToSlashes = dateWithHyphens.replace(/-/g, "/");


Libraries to the rescue: Fairy godmothers of code

Handling tricky date scenarios or trying to please every browser? Consider date-fns or Moment.js:

const date = moment('2011-04-12').toDate();


Explicit construction: The unwavering knight’s code

When all else fails, be clear and precise:

// Our knight's shield against cross-browser dragons
const explicitDate = new Date(2023, 0, 2, 0, 0, 0, 0);


Testing: Your trusty scouts in browser kingdom

Send tests into Safari's dark forests. Return victorious:

console.log(new Date('2023/01/02')); // If this logs without an error, you'll return a hero


The browser taxonomy: Understanding species and their peculiarities

Browsers are like distinct species in a digital ecosystem. Safari is the elusive snow leopard with unique parsing behavior.

Unraveling Safari’s distinct trail

Safari seems to favor the American style dates (MM/DD/YYYY) and is fussier with ISO 8601 (YYYY-MM-DD) compared to other species (Chrome, Firefox).

Survival tip: Update to adapt

Like species evolving over time, browser versions change their diet. An old Safari and the latest edition might not digest the same date diet.

Universal language: Millisecond timestamps

Use getTime() for timestamps in milliseconds to speak the only universal language recognized by every browser.

Knowledge for survival: The browser safari guide

Arm yourself with knowledge from MDN, ECMA-262, and tool libraries to survive in the wild. Unravel the mysteries of Safari's peculiarities to fight the Invalid date monster!