Inconsistent DateTime format when using toLocaleString

I don’t know if this is related to something on my MacBook, but for some reason, my tests started failing with this:

const timestamp = "2022-05-11T23:23:00-07:00";  // Example timestamp string
DateTime.fromISO(timestamp, { zone: 'America/Los_Angeles' }).toLocaleString(DateTime.DATETIME_FULL);

On any other machine, this is the sample formatted output, but should be correct according to the documentation: May 12, 2022, 7:00 AM PDT

On my Macbook, I would get this instead: May 12, 2022 at 7:00 AM PDT

• OS: MacOS 13.0.1
• node.js version: 19.1.0
• Luxon version: 3.1.0
• Timezone: America/Los_Angeles

[icambron]

I agree that users of Luxon shouldn’t be testing against the output of toLocaleString; they should merely test that the inputs to Luxon are what they think they should be.

However, Luxon itself needs to test, at the very least, that the inputs it sends to Intl are right. It doesn’t currently have a good way to do that, so we test the output of toLocaleString too. A refactor that gave us an Intl mock that we could assert against would fix this problem in Luxon’s own tests.

[inomn]

Hey everyone. Tried out my test on Node19 and here’s what I got (works well on node 16, 17, 18):

In Node 19 space character code is 8239 and in “older” Node, including current LTS it’s 32

Any ideas on a workaround?

Same space issue with both DateTime.fromISO(date).toLocaleString(XXX) and DateTime.fromISO(date).toFormat(XXXX, { locale })