Install

Works with Drupal: ^10.3 || ^11

Using Composer to manage Drupal site dependencies

Alternative installation files

Download tar.gz 760.84 KB
MD5: bb336d8bda8daf93260f54d257b4653e
SHA-1: ce1980ba4917d17463e072a65e65188e33bee682
SHA-256: 47ef421c21f29459aea90144aeaa5670caa356ec82725dd5d4ea78a29d9171fa
Download zip 1.27 MB
MD5: 9c38d13fab28812c477ef2e2d62e1c1a
SHA-1: 77e8ac37078f3a3a7f465f4383116a7598ca6e2f
SHA-256: 0fafb7c526d6d08d918ac64a4f6a884e949bebcc4725c8fb7bc7abb78013172d

Release notes

Changed
- Module and theme install/uninstall hooks no longer resolve npm dependencies over the network. The hooks synchronously re-resolved the whole dependency graph against registry.npmjs.org whenever the enabled extension set changed, putting minutes of network I/O inside the module install lifecycle: pm:install depended on registry availability, and on hosts with a low MySQL wait_timeout the idle connection died mid-install ("MySQL server has gone away" with half-written caches). The hooks now only check staleness against local files and log an actionable notice; drush sdx:resolve - which has always reconciled the lockfile itself before installing - is the single place resolution happens. A new status
report row ("SDX: Dependency lockfile") warns while sdx.lock is out of date.
Installing SDX modules now works fully offline.

Fixed
- Cold dependency resolution fetches registry package documents through a bounded concurrent pool instead of one serial round-trip per package. A large manifest set resolves in a few seconds instead of minutes, and because each response is cached to the database as it settles, the connection sees regular activity for the whole phase - closing the "gone away" window that remained in sdx:resolve's resolution phase after 1.0.0-alpha12 covered the install child process. Failed fetches fall back to the sequential path, which reports them with full context.

Created by: vzsigmond
Created on: 9 Aug 2026 at 22:34 UTC
Last updated: 9 Aug 2026 at 22:34 UTC
Bug fixes

Other releases