-
**Describe the bug**
When my jest config and srcs are under directory with `.nvmrc`, then the proper version of the node is not used for running jest tests. It used just the default.
**To Reproduc…
-
## Describe the Bug
When trying to resolve latest lts node version, I'm getting the result I was not expecting. When I run `asdf nodejs resolve lts` it only outputs a current major number `18` inst…
-
We should update the node engine used in our projects: https://github.com/pressbooks/pressbooks/blob/a2cc8dfa8fa7891d6ab9c2b56ea204023f6f2fc2/package.json#L16
Would also be nice to have a .nvmrc fi…
-
### Description of your issue:
When my rails project has a `.nvmrc` file, ci builds fail silently at the `postgres_start` step
failing build:
https://app.shippable.com/github/8834130/sp-fulfi…
-
After cloning a fresh network repo, the pesky build errors surrounding `deployOldUpgradableVersions` have re-appeared. I'm creating an issue here to keep better track of things, as I expect this file …
-
Forgive me if this has been discussed before, but I didn't find anything beyond https://github.com/creationix/nvm/issues/110#issuecomment-40525629.
It would be really nice to see the various Node ver…
-
Awesome feature! I've been using the following config:
**: [${dirname}] ${filename}.${extname}
However, there's a slight problem with dot files. (e.g. `.zshrc`)
The above config renders it as `…
-
**#40 Review it and Need a new interface for this Curatedstack Template!**
-
-
Run `nvm use` will read local package.json's engines.node and change version accordingly.
Or anyway that auto switch the version.