@hmcts/opal-frontend-common-node v0.0.8

OPAL Frontend Common Node Library

This is a shared Node.js library containing common middleware, configurations, and utilities used across OPAL backend services.

Table of Contents

• Getting Started
• Scripts
• Build Process
• Linting and Formatting
• Exports
• Using This Library in a Node.js Application
• Switching Between Local and Published Versions

Getting Started

Prerequisites

Ensure you have the following installed:

• Node.js v18 or later
• Yarn v1.22.22 or later

Install Dependencies

yarn

Build Process

Run the following to build the project:

yarn build

The compiled output will be available in the dist/ folder. It includes index.js, type declarations, and any exported modules listed in the exports field.

Switching Between Local and Published Versions

See opal-frontend for how this library is consumed in practice.

Use the yarn import:local:common-node-lib and yarn import:published:common-node-lib scripts in your consuming project (opal-frontend) to switch between local development and the published npm version of the library.

To use a published version of this library during development in another project: 1. In the consuming project, run:

```bash
yarn import:published:common-node-lib
```

To use a local version of this library during development in another project:

1. Build this library:

   yarn build

2. In your consuming project (e.g. opal-frontend), ensure you have set an environment variable pointing to the local build:

   # In your shell config file (.zshrc, .bash_profile, or .bashrc)
   export COMMON_NODE_LIB_PATH="[INSERT PATH TO COMMON NODE LIB DIST FOLDER]"

3. In the consuming project (e.g. opal-frontend), run:

   yarn import:local:common-node-lib

   This will remove the published version and install the local build using the path provided.

4. To switch back to the published version:

   yarn import:published:common-node-lib

This setup makes it easy to switch between development and production versions of the shared library.

Publish the library

Once any changes have been approved and merged into the main branch, you'll need to publish a new version of the library so that it can be consumed by other projects. To do this:

1. Increment the version number in both the library's root package.json.
2. Commit and push those changes to the main branch.
3. On GitHub, create a new release and use the updated version number as a tag.
4. When the release workflow completes, the library will be published.

After this new version of the library is published, any consuming application should remove the local or outdated version of the library and then install the published version by running:

```bash
yarn import:published:common-node-lib
```

Linting and Formatting

To lint and check formatting:

yarn lint

To fix formatting issues automatically:

yarn prettier:fix

Exports

This library exposes multiple entry points under the exports field of package.json. Example usage:

import { CSRFToken } from '@hmcts/opal-frontend-common-node/csrf-token';
import { AppInsights } from '@hmcts/opal-frontend-common-node/app-insights';
import { Helmet } from '@hmcts/opal-frontend-common-node/helmet';
import { LaunchDarkly } from '@hmcts/opal-frontend-common-node/launch-darkly';
import {
  ExpiryConfiguration,
  RoutesConfiguration,
  SessionStorageConfiguration,
  TransferServerState,
} from '@hmcts/opal-frontend-common-node/interfaces';

Refer to the exports block in package.json for the full list of available modules.

Commonly Used Commands

The following commands are available in the package.json:

• yarn build
  Cleans the dist/ folder, compiles TypeScript, and copies relevant files to dist/.

• yarn clean
  Removes the dist/ directory.

• yarn lint
  Runs ESLint across the src/ directory and checks formatting using Prettier.

• yarn prettier
  Checks if files are formatted correctly.

• yarn prettier:fix
  Automatically formats the codebase.