Repository navigation
docs: state the supported Node.js versions and tested Nuxt releases - #236
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The README now states which Node.js versions Nuxt UTM supports: the release lines the Node.js project still maintains, currently 22, 24, and 26. These are the versions the CI matrix already tests. Node.js 18 and 20 have reached end of life and are outside that set.
Support is documented, not enforced. The package still has no
enginesfield. Yarn 1 fails an install when an engine range doesn't match, so a range would block apps on Nuxt releases that still accept Node.js 20, although no incompatibility is known. Nuxt and Nuxt Kit declare their own Node.js requirements, so any other version they accept stays installable but untested.The same paragraph says which Nuxt releases CI tests: the latest Nuxt 3 and Nuxt 4 releases and Nuxt 5 nightly builds. Earlier minor releases are untested, but nothing blocks them. The module's
compatibility.nuxtstays>=3.0.0and the Nuxt Kit dependency stays^3.17.2 || ^4.0.0. Nuxt disables a module whose compatibility range doesn't match the app, so narrowing either would switch capture off for existing apps with only a build warning.The development section now refers to "each supported Node.js version" instead of repeating the list. When the CI matrix changes, only the Setup paragraph needs to change with it.
Release note: Node.js 22, 24, and 26 are supported, and CI tests the latest Nuxt 3 and 4 releases and Nuxt 5 nightly builds. Other versions are untested but not blocked at install time.
Validation: this changes only the README.
prettier --check README.mdpasses.npm view nuxt-utm@0.4.0 enginesreturns nothing, so the published package doesn't restrict Node.js either, and@nuxt/kit@4declares^20.19.0 || >=22.12.0. The compatibility job'sNUXT_VERSIONvalues3,4, andnpm:nuxt-nightly@5xresolve to Nuxt 3.21.11, 4.6.1, and a 5.0.0 nightly.