Skip to content

Use a development release

Install a published build of the develop branch from the npm dev tag to try a fix or a feature before the next stable release.

A development release is a published build of the develop branch. Use one to try a fix or a feature before the next stable release.

The dev tag

A merge to develop that adds or changes a changeset is published to npm under the dev tag. A merge without one, such as a change to tests, tooling or documentation, publishes nothing, so the tag moves less often than the branch. A development release never moves the stable latest tag, so nobody gets one by accident.

A version reads 0.24.1-dev.20260920043715:

Part Meaning
0.24.1 The version the unreleased changes add up to
dev The channel
20260920043715 When it was built, in UTC

Every package in a build shares that timestamp, and each pins the other Druxt packages it needs to that exact build.

When publishing is on, the tag can move several times a day. It is switched off at the moment, so the tag stays at its last build until it resumes. See where the tags point:

npm dist-tag ls druxt

Who it is for

  • Confirming on your own site that a reported bug is fixed.
  • Catching a regression in a module or a site before a release.

A development release has passed the test suite, and that is all. It can contain breaking changes and unfinished work. Pin the exact version, and do not deploy one to production without testing it first.

Opt in

Install druxt-site from the dev tag:

npm i druxt-site@dev

The other Druxt packages come with it at the matching build.

If your package.json lists other Druxt packages, such as druxt-menu or druxt-views, move each of them to @dev too, or remove the ones you do not import directly. A package left on a stable version installs a second copy of Druxt beside the development one.

Make sure there is one copy of Druxt

Druxt registers Vuex stores and components, so a site needs exactly one copy of druxt.

A module from outside the Druxt repository, such as druxt-auth, asks for a stable druxt. No stable version range accepts a prerelease, so your package manager installs a second copy to satisfy it. Force one copy with the exact version you installed.

With npm, in package.json:

{
  "overrides": {
    "druxt": "0.24.1-dev.20260920043715"
  }
}

With Yarn:

{
  "resolutions": {
    "druxt": "0.24.1-dev.20260920043715"
  }
}

Then check:

npm ls druxt

One version in the output means it worked.

Follow the channel

The dev tag is resolved when you install, and the result is written to your lockfile. To move to a newer build, install druxt-site@dev again and update the override.

To have each new build arrive as a pull request, tell Renovate to follow the tag:

{
  "packageRules": [{ "matchPackagePatterns": ["^druxt"], "followTag": "dev" }]
}

Opt out

  1. Set druxt-site, and any other Druxt package you list, back to a stable range.
  2. Remove the overrides or resolutions entry.
  3. Install again.

Report a problem

Open an issue on druxt/druxt.js and include the full version, such as 0.24.1-dev.20260920043715. It names the exact build.