Skip to content

Commit

Permalink
chore: package-lock changes due to npm install (node v14.21.3) (#350)
Browse files Browse the repository at this point in the history
  • Loading branch information
cameronhunter committed Apr 13, 2024
1 parent 18ba799 commit da49e57
Show file tree
Hide file tree
Showing 3 changed files with 80 additions and 73 deletions.
1 change: 1 addition & 0 deletions .nvmrc
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
14
12 changes: 9 additions & 3 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,13 +29,19 @@ This project adheres to the American Express [Code of Conduct](./CODE_OF_CONDUCT

> replace `your-github-username` with your github username
3. Install the dependencies by running
3. Install and use the correct version of node (specified in `.nvmrc`)

```bash
$ nvm use
```

4. Install the dependencies by running

```bash
$ npm install
```

4. You can now run any of these scripts from the root folder.
5. You can now run any of these scripts from the root folder.

#### Running tests

Expand Down Expand Up @@ -112,4 +118,4 @@ Please review our [Security Policy](./SECURITY.md). Please follow the instructio

### Git Commit Guidelines

We follow [conventional commits](https://www.conventionalcommits.org/) for git commit message formatting. These rules make it easier to review commit logs and improve contextual understanding of code changes. This also allows us to auto-generate the CHANGELOG from commit messages.
We follow [conventional commits](https://www.conventionalcommits.org/) for git commit message formatting. These rules make it easier to review commit logs and improve contextual understanding of code changes. This also allows us to auto-generate the CHANGELOG from commit messages.
140 changes: 70 additions & 70 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

0 comments on commit da49e57

Please sign in to comment.