-
I noticed a case where renovate would bump the `engines.node` field in `package.json` from 16.13 to 16.15, but not update the corresponding line in `.nvmrc` resulting in CI failures. Ideally, we would…
-
For a given project, we want to ensure that:
- The project has a `README.md`. Past this, we want to ensure that:
- It has a single, non-empty H1.
- It has at least these H2 headers with non-e…
-
Provide feedback and elaborate on README as you go.
-
Run `nvm use` will read local package.json's engines.node and change version accordingly.
Or anyway that auto switch the version.
-
From a discussion on Discord, along with the multiple questions we've had around using `engines` instead of the custom `volta` key in `package.json`: One possible way to improve interoperability and c…
-
### Unable to start MySQL service
When adding the following stanza to the `shippable.yml` we are encountering a build failure in the `mysql_start` step.
```
services:
- mysql
```
#### Su…
-
In order to easily move the project between environments (local dev, heroku, CI, etc.), I want to know which version of node and npm the project is meant to run under.
I know that heroku [looks for](…
rylnd updated
8 years ago
-
Otherwise, the default version of node that is currently used is v8. For example, see this build log: https://app.netlify.com/sites/containerd-io/deploys/62dae776ae6e5900087c5111
```nocode
Now usi…
-
Instead of hard coding the version in the workflow, it would be nice to have it read it from a file similar to how [`actions/setup-node@v3`](https://github.com/actions/setup-node) reads from `.nvmrc`
…
-
```
"engines": {
"node": "12.13.1"
},
```
it helps to use correct environment