@ebot7/javascript-sdk NPM

Ebot7 Javascript SDK

ebot7 Javascript SDK.

This is the ebot7 Javascript Software Development Kit (JS SDK) Package.

The JS SDK is a thin client for developing and testing aspects of the ebot7 Application.

It has been set up with automated unit tests and package publishing workflow using GitHub Actions CI/CD.

It uses npm, TypeScript Compiler, Jest, ESLint, Prettier and cspell. The production files include CommonJS, ES Modules, UMD version and TypeScript declaration files.

Development

Environment

You need to have Node.js installed. Node includes npm as its default package manager.

Installation

Install dependencies with yarn:

yarn install

Write your code

Make necessary changes in package.json (name, version, description, keywords, author, homepage and other URLs).

Write your code in src folder, and unit test in test folder, replacing the original files there.

Test

Test all aspects of the code (Prettier, ESLint, and Jest) with:

yarn test

Optionally run individual tests using any or the below:

Prettier:   yarn test:prettier
Spelling:   yarn test:spelling
ESLint:     yarn test:eslint
Unit Test:  yarn test:unit

Build

Build production (distribution) files in your build folder:

yarn build

It generates CommonJS (in build/main folder), ES Modules (in build/module folder).

Try it before publishing

Run:

npm link

npm link will create a symlink in the global folder, which may be {prefix}/lib/node_modules/@bot7/javascript-sdk or C:\Users\\AppData\Roaming\npm\node_modules\@ebot7\javascript-sdk.

Create an empty folder elsewhere, you don't even need to npm init (to generate package.json). Open the folder with VS Code, open a terminal and just run:

npm link @ebot7/javascript-sdk

This will create a symbolic link from globally-installed example-typescript-package to node_modules/ of the current folder.

You can then create a, for example, test-client.ts file with the content:

import { Client } from '@ebot7/javascript-sdk';

If you don't see any linting errors in VS Code, if you put your mouse cursor over Client and see its type, then it's all good.

Whenever you want to uninstall the globally-installed package and remove the symlink in the global folder, run:

npm uninstall @ebot7/javascript-sdk -g

Prepare to publish

Create an npm account.

Manual publishing to npm

npm adduser

And publish:

npm publish

This package is configured to use GitHub Actions CI/CD to automate both the npm and GitHub Packages publishing process. The following are what you have to do.

CI publishing to npm

Follow npm's official instruction to create an npm token. Choose "Publish" from the website, or use npm token create without argument with the CLI.

If you use 2FA, then make sure it's enabled for authorization only instead of authorization and publishing (Edit Profile -> Modify 2FA).

On the page of your newly created or existing GitHub repo, click Settings -> Secrets -> New repository secret, the Name should be NPM_TOKEN and the Value should be your npm token.

CI publishing to GitHub Packages

The default configuration of this example package assumes you publish package with an scoped name to npm.

(You might have noticed secret.GITHUB_TOKEN in .github/workflows/test.yml. You don't need to set up a secret named GITHUB_TOKEN actually, it is automatically created)

Publish

Now everything is set. The example package has automated tests and upload (publishing) already set up with GitHub Actions:

Every time you git push or a pull request is submitted on your master or main branch, the package is automatically tested against the desired OS and Node.js versions with GitHub Actions.
Every time an annotated (not lightweight) "v*" tag is pushed onto GitHub, a GitHub release is automatically generated from this version, it also automatically publishes to the npm registry and/or GitHub Packages registry to update the package there.
- npm version / yarn version is useful to create tags.
- You could also add "postversion": "git push --follow-tags" to package.json file to push it automatically after npm or yarn version. (for yarn version only: because yarn version doesn't check whether there are uncommitted changes, you can add "preversion": "git diff-index --quiet HEAD --" to package.json)

For npm registry: you can unpublish a version or the whole package but can never re-publish the same version under the same name.

If you want to modify the description / README on the npm package page, you have to publish a new version. You can modify the description on GitHub Packages without publishing.

Notes

It uses npm but you can easily switch to yarn, of course (remember to change all "npm" in scripts in the file package.json)
- Whether you use npm as your package manager ≠ Whether you can publish to the npm registry
Works fine in VS Code. In my configuration .eslintrc and .prettierrc cooperate perfectly
See scripts in package.json for other predefined script commands