@handy-common-utils/dev-utils v1.7.0

@handy-common-utils/dev-utils

Tool chain utilities for the convenience of developers.

Node.js version compatibility

• Test cases have been verified with Node.js versions 14, 16, and 18.
• Compilation targe is ES2017.
• Compatibility with ES2017 has been checked.

How to use - generating API doc and update README.md

Normally you don't use this package directly (although it is perfectly fine to use this package alone). Instead, you add @handy-common-utils/dev-dependenciesas a dev dependency (which in turn depends on this package):

npm install -D @handy-common-utils/dev-dependencies

After installation, the command line generate-api-docs-and-update-readme will be available in your project. This command line can update the <!-- API start -->...<!-- API end --> section in your README.md with generated API documentation.

You can use optional command line arguments to customise the behaviour of generate-api-docs-and-update-readme:

1. Path of the readme.md file. The path must ends with ".md" (case insensitive). The file would be modified. Default: README.md.
2. Entry points for generating API documentation. Multiple entry points can be specified by joining them with comma (,). Default: ./src.
3. path of the directory for storing generated intermediate documentation files. This directory would not be cleaned up. Default: api-docs.

These arguments must be specified in the order as shown above.

How to use - getGitInfo(...)

const info = await DevUtils.getGitInfo(); is how you can get Git repository related information, such as repository, branch, commit id, tags, etc. It relies on the Git command line tool ('git') to have already been installed.

The function accepts two optional arguments. The first one allows you to specify which properties/info to return. The second one allows you to control whether environment variables should be checked. By default all properties/info would be returned and environment variables would be checked before falling back to checking local Git repository.

Checking environment variables is handy when you use it in a build/CI/CD pipeline.

Below is an example output:

{
  message: 'user and email could be undefined in CI',
  email: 'james.hu.ustc@hotmail.com',
  user: 'James Hu',
  describeLight: 'v1.0.26-3-g6cfaeb8',
  describe: 'v1.0.26-3-g6cfaeb8',
  isDirty: true,
  branch: 'feature/git-info',
  commitIdLong: '6cfaeb8dade5c374c5dcc1e440795aeab3951fa9',
  commitIdShort: '6cfaeb8',
  repository: 'dev-utils',
  messageBody: '',
  messageSubject: 'user and email could be undefined in CI',
  tag: '6cfaeb8',
  tags: [ '6cfaeb8' ]
}

Details of the properties in this structure can be found in the documentation of GitInfo interface.

The functionality depends on serverless-plugin-git-variables. Check it out if you are interested.

How to use - loadConfiguration(...) and loadConfigurationWithVariant(...)

The function loadConfiguration(...) / DevUtils.loadConfiguration(...) would be handy if you need to read configuration from YAML and/or JSON files.

If you have multiple variants of the configurations, such like settings.default.yml, settings.staging.yml, settings.production.yml, you can use loadConfigurationWithVariant(...) or DevUtils.loadConfigurationWithVariant(...) instead.

loadConfiguration(...) / DevUtils.loadConfiguration(...) has these features:

• Find and parse files in the same directory with different extensions. By default it picks up and parses .yaml, .yml and .json files, but you can customise file extensions and the order they override each other. You can also customise it to pick up different versions of configuration files, such like: {'-v3.yml': 'yaml', '-v2.yml': 'yaml', '.json': 'json'}
• Find and parse files in ancestor (parent, grandparent, etc.) directories as well. This is not the default behaviour, but you can provide a predicate function to options.shouldCheckAncestorDir for customising this behaviour. If configuration files exit in both parent and child directories, the configuration in the child directory overrides that in the parent directory.
• Although you may not need it, you can customise how configurations are merged by providing the merge function to options.merge.
• If the configuration file does not exist, it would just be silently ignored.
• If the configuration file has a format/syntax error and can't be parsed, an Error would be thrown.
• If there's no configuration file picked up, it would return undefined.

loadConfigurationWithVariant(...) / DevUtils.loadConfigurationWithVariant(...) has these additional features:

• Allows a base variant and an interested variant to be specified
• Overrides the base variant configuration with the interested variant configuration

Code examples:

// Pick up and merge (those to the left overrides those to the right) configurations from: ./my-config.yaml, ./my-config.yml, ./my-config.json
const config = DevUtils.loadConfiguration('my-config');

// Pick up and merge ./my-config.default.{yaml,yml,json} with ./my-config.prod.{yaml,yml,json}
const config = DevUtils.loadConfigurationWithVariant('my-config', '.prod');

// Pick up and merge ./my-config-production.{yaml,yml,json} with ./my-config.{yaml,yml,json}
const config = DevUtils.loadConfigurationWithVariant('my-config', '-production', '');

// Let .json override .yml and don't try to pick up .yaml
const config = DevUtils.loadConfiguration('my-config', { extensions: {
  '.json': 'json',
  '.yml': 'yaml',
} });

// Pickup and merge (v3 overrides v2 overrides legacy) my-config-v3.yml, my-config-v2.yml, my-config.json
const config = DevUtils.loadConfiguration('my-config', { extensions: {
  '-v3.yml': 'yaml',
  '-v2.yml': 'yaml',
  '.json': 'json',
} });

// Search in parent, grand parent, and great grand parent directories as well
const config = DevUtils.loadConfiguration(
  'my-config',
  {
    dir: 'test/fixtures/dir_L1/dir_L2/dir_L3/dir_L4',
    shouldCheckAncestorDir: (level, _dirName, _dirAbsolutePath) => level <= 3,
  },
);

How to contribute

Please note that for avoiding peer dependency serverless to be included, bundled dependency serverless-plugin-git-variables was installed with additional option:

npm i serverless-plugin-git-variables --legacy-peer-deps

API

Module: dev-utils

Re-exports

Functions

• generateApiDocsMd = DevUtils.generateApiDocsMd
• generateApiDocsAndUpdateReadme = DevUtils.generateApiDocsAndUpdateReadme
• getGitInfo = DevUtils.getGitInfo
• loadConfiguration = DevUtils.loadConfiguration
• loadConfigurationWithVariant = DevUtils.loadConfigurationWithVariant

Exports

Classes

• DevUtils

Interfaces

• GitInfo
• LoadConfigurationOptions

Type Aliases

GitInfoKey

Ƭ GitInfoKey: keyof GitInfo

Classes

Class: DevUtils

dev-utils.DevUtils

Constructors

constructor

• new DevUtils()

Properties

Methods

generateApiDocsAndUpdateReadme

▸ Static generateApiDocsAndUpdateReadme(readmeLocation?, entryPoints?, apiDocDir?, typeDocOptions?): Promise<void>

Generate API documentation and insert it into README.md file.

Example

DevUtils.generateApiDocsAndUpdateReadme(readmePath, entryPoints, apiDocDir);

Parameters

Returns

Promise<void>

Promise of void

generateApiDocsMd

▸ Static generateApiDocsMd(entryPoints?, apiDocDir?, options?): Promise<void>

Parameters

Returns

Promise<void>

getGitInfo

▸ Static getGitInfo(whitelistKeys?, checkEnvironmentVariables?, reportErrors?): Promise<Partial<GitInfo>>

Get Git related information. This function relies on the existence of Git command line.

By default all possible information will be returned, but this can be overridden by specifying whitelistKeys argument.

If checkEnvironmentVariables argument is true, then environment variables GIT_COMMIT and GITHUB_SHA will be checked before trying to identify the commit ID from local Git repository, also environment variables GIT_LOCAL_BRANCH, GIT_BRANCH, BRANCH_NAME, GITHUB_REF_NAME will be checked before trying to identify the branch name from local Git repository.

This function never throws Error. For example, if user and email have not been configured, they would be undefined in the returned object.

Parameters

Returns

Promise<Partial<GitInfo>>

Git related information

loadConfiguration

▸ Static loadConfiguration<T>(fileNameBase, overrideOptions?): undefined | T

Load configuration from YAML and/or JSON files. This function is capable of reading multiple configuration files from the same directory and optionally its ancestor directories, and combine the configurations.

Internal logic of this function is: \ 1. Start from the directory as specified by options.dir (default is ".") \ 2. Try to read and parse all the files as specified by ${dir}${options.extensions.<key>} as type options.extensions.<value> \ 2.1 Unreadable (non-existing, no permission, etc.) files are ignored \ 2.2 File content parsing error would halt the process with an Error \ 2.3 Files specified at the top of options.extensions overrides those at the bottom \ 2.4 Default configuration in options.extensions is: ".yaml" as YAML, ".yml" as YAML, ".json" as JSON. You can override it. \ 3. Find the parent directory, and use options.shouldCheckAncestorDir function to decide if parent directory should be checked. \ 3.1 The function won't be called for the starting directory. The first call to this function would be for the parent directory with level=1. \ 3.2 If parent directory should be checked, use parent directory and go to step 2 \ 3.3 Otherwise finish up \ 3.4 Default configuration of options.shouldCheckAncestorDir always returns false. You can override it. \ 3.4.1 Several parameters are passed to the function: level (the immediate parent directory has the level value 1), basename of the directory, absolute path of the directory, already consolidated/merged configurations, absolute path of the directory containing the last/previous file picked up. \ 4. Configurations in child directories override configurations in parent directories. \

Other options: \ encoding: encoding used when reading the file, default is 'utf8' \ merge: the function for merging configurations, the default implementation uses lodash/merge \

Example

// Pick up and merge (those to the left overrides those to the right) configurations from: ./my-config.yaml, ./my-config.yml, ./my-config.json
const config = DevUtils.loadConfiguration('my-config');

// Let .json override .yml and don't try to pick up .yaml
const config = DevUtils.loadConfiguration('my-config', { extensions: {
  '.json': 'json',
  '.yml': 'yaml',
} });

// Search in parent, grand parent, and great grand parent directories as well
const config = DevUtils.loadConfiguration(
  'my-config',
  {
    dir: 'test/fixtures/dir_L1/dir_L2/dir_L3/dir_L4',
    shouldCheckAncestorDir: (level, _dirName, _dirAbsolutePath) => level <= 3,
  },
);

Type parameters

Parameters

Returns

undefined | T

The combined configuration, or undefined if no configuration file can be found/read.

loadConfigurationWithVariant

▸ Static loadConfigurationWithVariant<T>(fileNameBase, variant, baseVariant?, overrideOptions?): undefined | T

Load configuration from YAML and/or JSON files with variant suffix. This function is capable of reading multiple configuration files from the same directory and optionally its ancestor directories, and combine the configurations. This function is based on loadConfiguration. It picks up the specified variant configuration and the base variant configuration from a directory and optionally its ancestor directories, then merge them by overriding the base variant configuration with the specified variant configuration.

Type parameters

Parameters

Returns

undefined | T

The combined configuration, or undefined if no configuration file can be found/read.

Interfaces

Interface: GitInfo

dev-utils.GitInfo

Git related information. See https://github.com/jacob-meacham/serverless-plugin-git-variables

Properties

Interface: LoadConfigurationOptions<T>

dev-utils.LoadConfigurationOptions

Options for loadConfiguration(...) function

Type parameters

Properties