ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
When a Markdown file contains a date in front matter without an explicit UTC offset, Eleventy parses it as a local JavaScript Date using the host’s time zone unless a global timezone setting is supplied. The resulting Date object is stored in the collection and used for sorting, but the date filter in Nunjucks/Liquid formats it according to the runtime’s zon
Integration Boundary: Akka HTTP & java.time The goal is to ensure that HTTP requests containing an ISO‑8601 formatted Date header are correctly interpreted by an Akka HTTP service that otherwise relies on java.time for time‑zone handling. Akka HTTP’s current HttpDate parser accepts only RFC1123, RFC1036, and ANSI C asctime formats, omitting ISO‑8601 and
I am building a web app that receives date-time strings from a backend and must display them converted to each user's regional time zone. The app needs to work reliably in Safari as well as Chrome and Firefox. My understanding is that Safari's Date parser is stricter than other engines. Strings like 2024-01-15 10:30:00 (space separator instead of the ISO T )
eleventy
akka