DruxtJS 0.25.0 Adds Drupal API Caching After Nearly Three Years

The Performance Gains Arrive on an End-of-Life Nuxt 2 Stack
A digital illustration shows data flowing from servers through transparent caching layers to desktop and mobile devices. The Drop Times graphic reads "DISCOVER DRUPAL" and "Fewer Requests, Less Repeated Work". Supporting text states "DruxtJS 0.25.0 introduces caching and request deduplication to reduce Drupal API traffic." The footer displays "https://www.thedroptimes.com/" alongside The Drop Times logo.

Following nearly three years without a JavaScript core package release, DruxtJS introduced version 0.25.0 on 23 October 2026, adding server-side caching, request deduplication and optional schema refresh for decoupled Drupal websites. Project creator Stuart Clark detailed the improvements in a technical release post. The release gap concerns the Nuxt-based JavaScript framework, rather than its Drupal-side integration, which received updates earlier in 2026.

The update aims to reduce repeated requests between a Nuxt frontend and Drupal's JSON:API backend. According to Clark's tests on the Druxt documentation website, requests to Drupal for a warm page fell from 17 to 11. Enabling content caching reduced requests to zero on the tested warm pages, while a separate 24-page cold crawl recorded a reduction from 438 requests to 157. These figures are developer-reported results rather than independent performance benchmarks.

In production, DruxtJS caches the JSON:API index and menus when Drupal's Cache-Control headers permit it, requiring a positive cache lifetime rather than Drupal's default maximum age of zero. Caching of content responses must be enabled separately, while authenticated requests remain excluded. Cache invalidation can be triggered through Drupal, although the current implementation clears the entire DruxtJS cache rather than selectively removing affected resources. The release also introduces optional schema refresh, allowing Drupal display configuration changes to be reflected without rebuilding a server-rendered frontend after cache clearing.

Despite these improvements, DruxtJS remains dependent on Nuxt 2, which reached end of life on 30 June 2024. Clark's roadmap identifies further maintenance releases before a planned rewrite for Nuxt 4 under Druxt 2.0.0. The new caching capabilities offer potential reductions in Drupal API traffic, but performance gains depend on deployment configuration, and the unsupported frontend dependency remains a consideration for existing installations.

References

  1. druxt release notes, DruxtJS (23 October 2026)

Disclosure: This content is produced with the assistance of AI.

Note: The vision of this web portal is to help promote news and stories around the Drupal community and promote and celebrate the people and organizations in the community. We strive to create and distribute our content based on these content policy. If you see any omission/variation on this please reach out to us at #thedroptimes channel on Drupal Slack and we will try to address the issue as best we can.

Upcoming Events

Latest Opportunities