Checkout the part 1, where I covered writing a very simple node package and publishing that to github packages.

In this post, we'll build on top of that. Rewriting the whole thing again, we'll add support for unit tests and github actions to run our tests and publish our package.

To avoid distractions, I intentionally didn’t put the source code in last blog. You can find it here. Let's get started.

Adding unit tests

1. To keep our code more manageable, let's create two new folders src and test

cd my-node-package
mkdir src test

src to hold our source code and test for . . . well, you might have guessed.

1. Move our source code to src folder (we have index.js file only 😊)

mv index.js src

1. We'll use jest JS testing framework. At this point our package.json should be changed to

{
    "name": "@<SCOPE>/rei-node-package",
    "version": "1.0.0",
    "description": "This is an example node package",
    "repository": "https://github.com/<SCOPE>/rei-node-package",
    "main": "src/index.js",
    "publishConfig": {
      "registry": "https://npm.pkg.github.com"
    },
    "devDependencies": {
      "jest": "^26.6.3"
    },
    "scripts": {
      "test": "jest"
    }
}

Notice the changes we made? We have changed main, added dependency(dev dependency) on jest and using jest for testing.

1. Next, let's add a test to test our very complex 😉 rei function. In test/index.test.js file

const rei = require('../src/index')

describe("rei package", () => {
  it("return: You have succesfull installed and ran lionbridgeai's rei package", () => {
    expect(rei()).toEqual("You have succesfull installed and ran lionbridgeai's rei package")
  })
})

1. Ready to run the tests? First do a npm install to install dependencies (jest) and then npm test.

➜  rei-node-package git:(master) npm test

> @lionbridgeai/rei-node-package@0.2.0 test
> jest

 PASS  test/index.test.js
  rei package
    ✓ return: You have succesfull installed and ran lionbridgeai's rei package (2 ms)

Test Suites: 1 passed, 1 total
Tests:       1 passed, 1 total
Snapshots:   0 total
Time:        1.145 s
Ran all test suites.

Hoping all your tests pass🤞

1. Let's publish our new version.

npm version major # you might have to commit your existing changes first
npm publish       # check part 1 of this blog series on how to publish

Using Github Actions

In this section we'll explore how to run tests whenever someone creates a PR to master for your package. And how to publish on every push to master

Github Actions reads instructions from workflow(.github/workflows) files and runs them. A workflow to run tests on every PR for master would look like(let's name it .github/workflows/build.yml)

name: build

on:
  pull_request:
    branches:
    - master

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - uses: actions/setup-node@v2
        with:
          node-version: 16
      - run: npm install
      - run: npm test

Now, whenever someone creates a PR, github actions would run the required tests and send the checks back to PR. It would be a very helpful input in deciding whether to merge the PR or not.

Next, let's add a workflow to publish our package whenever a push is made to master (either directly or a PR to master is merged). Workflow file (let's name it .github/workflows/publish.yml) would be like

name: publish

on:
  push:
    branches:
    - master

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - uses: actions/setup-node@v2
        with:
          node-version: 16
      - run: npm install
      - run: npm test
  publish:
    needs: build
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - uses: actions/setup-node@v2
        with:
          node-version: 16
          registry-url: https://npm.pkg.github.com/
      - run: npm publish
        env:
          NODE_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}}

Note that this workflow has two jobs build and publish. build job runs the tests(same as build.yml workflow we saw earlier) and publish simply publishes our package to github packages. Note the NODE_AUTH_TOKEN env var, it's set to GITHUB_TOKEN secret. This secret is automatically created for your repo and has permissions necessary to publish a package. Don't forget to update your package version whenever you create a PR or push to master. Or you can update the version while running publish workflow(take it as an exercise 😉).

That's all for now. Hope you find it helpful. Open to your feedback and suggestions to make the content more engaging and helpful.

Update: I'm publishing blogs as github issues now. You can find them here https://github.com/nakamorg/blogs/issues