- Issue created by @genebobmiller
- Status changed to Fixed
12 months ago 9:52am 14 July 2023 Changed to "5.0.x-dev" and pushed a fix there, also bumped the node version to v18.16.1 in
nvmrc. thanks for bringing this upthe 5.1.x-dev is not ready at all and might change quite drastically, I suggest not using that branch for now
- 🇲🇾Malaysia ckng
@doxigo, instead of using a fixed version number in the `.nvmrc`, we want to use `lts/hydrogen` for v18.* or `lts/gallium` for v16.* instead.
@ckng, never used it like so, would it always be the latest LTS version if you go with lts/hydrogen? and I wonder how that would play out with nvmrc
- 🇲🇾Malaysia ckng
@doxigo, it won't force the latest version, but the related major LTS version on the local that fulfill the requirement. In this case, user are not forced to use a specific version, as long as it is the same LTS major version.
Automatically closed - issue fixed for 2 weeks with no activity.