runs-on:ubuntu-latest

steps:

-uses:actions/checkout@v3

-uses:actions/setup-node@v3

with:

node-version:16

-name:📦 Install dependencies

run:npm ci

-name:🧪 Run tests

run:npm test

-name:🧪 Run all tests

if:${{ github.event_name == 'push' }}

run:npm run test

-name:🧪 Run tests for changed files only

if:${{ github.event_name == 'pull_request' }}

run:npm run test-changed

-name:💄 Code style

run:npm run style

npm run style

npm runtest

npm run test-changed

We use the[ES Module](https://hacks.mozilla.org/2018/03/es-modules-a-cartoon-deep-dive/) system, which bring an official, standardized module system to JavaScript.

We use the[ES Module](https://hacks.mozilla.org/2018/03/es-modules-a-cartoon-deep-dive/) system, which bring an

official, standardized module system to JavaScript.

It roughly means you will need to use`export` and`import` statements instead of`module.exports` and`require()`.

Be confident that your code works. When was the last time you committed a code change, your build failed, and half of

your app stopped working? Mine was last week. Writing tests for our Algorithms will help us ensure the implementations

areair tight even after multiple fixes and code changes.

areairtight even after multiple fixes and code changes.

We use[Jest](https://jestjs.io/) to run unit tests on our algorithms. It provides a very readable and expressive way to

structure your test code.

npmtest -- --watchAll

We also prepared a helper script that runs tests only for changed files:

npm run test-changed

This will run all tests and watch source and test files for changes. When a change is made, the tests will run again.

"type":"module",

"description":"A repository for All algorithms implemented in Javascript (for educational purposes only)",

"scripts": {

"test":"jest --no-cache",

"test":"jest",

"test-changed":"jest --onlyChanged",

"style":"standard",

"prepare":"husky install"

},