Dev Feed

One timezone being accepted correctly would probably suffice? And perhaps one malformed timezone not accepted?

Today [chrome-cookies-secure@canary](https://www.npmjs.com/package/chrome-cookies-secure/v/3.0.3-canary.0) was released with security updates [flagged by socket.dev](https://socket.dev/npm/package/chrome-cookies-secure/alerts/3.0.2?tab=dependencies). The package is currently best-effort maintained and is problematic to carry out major upgrades on because it runs cross-platform (macOS, Windows & Linux) and it doesn't have cross-platform tests setup (yet). I know this needs improving, but in the mean-time at least macOS based tests pass on this new version, and people can use it / test it out on other platforms with a smaller blast radius of security risks.

I wanted a way to post on the move to this feed without any extra cost. Enter Airtable: it can work as an input source via mobile app and web and be mapped to this feed with a little API action on the backend. This is my test post.

Thanks, this dropped off my radar in the end. Appreciate the PR. I've added some review comments.

Worth adding a test for timezone support?

No error message here?

Interesting. This output was from the built-in Cursor terminal. I just tried this in `Warp` & it worked, so this is CLI tech specific 🤔

Version: 0.55.2 (tested latest) & 0.54.0 (version I usually run on) ``` npx dprint fmt --config dprint.json --config-discovery=ignore-descendants thread 'tokio-runtime-worker' (29448642) panicked at /rustc/ed61e7d7e242494fb7057f2657300d9e77bb4fcb/library/alloc/src/slice.rs:520:23:

Similar error here for reference: https://github.com/privatenumber/tsx/issues/640

Did this get fixed then? Comment in Aug 2022 says it was scheduled for upcoming 4.x beta, but we're now on version 5. It's marked as `Low Priority`, and isn't closed, so I'm guessing it still doesn't work as expected?