Skip to content

emdash@0.18.0

Choose a tag to compare

@emdashbot emdashbot released this 11 Jun 19:49
849628f

Patch Changes

  • #1391 8a766b8 Thanks @mvvmm! - Add fetchpriority="high" to priority EmDash images so above-the-fold images can be requested eagerly and prioritized by the browser.

  • #1405 bdabff7 Thanks @ascorbic! - Fixed a bug where a visitor disconnecting at the wrong moment during a cold start could leave that server instance permanently broken: every subsequent request to it would hang until the platform timed it out (a 524 error on Cloudflare, after 100 seconds), and the instance stayed broken until it was recycled. Sites no longer get stuck — startup now recovers automatically, and in the worst case a request fails fast with an error instead of hanging.

  • #1408 afc065c Thanks @ascorbic! - Faster cold starts. The first request a fresh server instance handles — after a deploy, or when traffic picks up again after a quiet spell — now runs its startup steps concurrently instead of one at a time, shaving database and storage round trips off that first page load. Especially noticeable on Cloudflare, where new instances spin up frequently.

  • #1409 7ee9467 Thanks @ascorbic! - Pages render with fewer database round trips:

    • Tag and category archive pages load faster — getTerm() fetches its details in parallel instead of one query at a time.
    • Pages with several menus (header, footer, …) no longer repeat the same lookup for each menu.
    • Entries fetched with getEmDashEntry/getEmDashCollection already include their taxonomy terms — you can now read entry.data.terms?.tag directly (it's typed in your generated emdash-env.d.ts) instead of making a separate getEntryTerms() call. The bundled templates have been updated to do this.
  • #1407 f9362d7 Thanks @ascorbic! - Query instrumentation (EMDASH_QUERY_LOG=1) now captures the whole request, not just the part before the response headers are sent. Queries issued by components while the page is still streaming were previously invisible to the Server-Timing numbers; a final [emdash-stream-end] log line now reports the complete query count, database time, and cache hits for each request, so you can see where a slow page really spends its time. No effect when instrumentation is off.

  • Updated dependencies [d2829e3]:

    • @emdash-cms/admin@0.18.0
    • @emdash-cms/auth@0.18.0
    • @emdash-cms/gutenberg-to-portable-text@0.18.0