Adopt `package.json` support information

Open
#10 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
node.js
Domain
build-system

Research direction

Start by locating the NPM package package.json files and the existing CI/CD automation in this repository. Review the support-information proposal and the @pkgjs/nv mapping mentioned in the issue; confirm the intended package fields and Node.js engine update behavior before making changes. Done means the packages expose standardized support information and the engine-bump basis is established.

Written by the indexing model from the issue text.

Description

This issue is to track the addition of package support information to our NPM packages.

This can also be used as the basis for automatically bumping the Node.js engine in package.json.

@pkgjs/nv can be used to map the Node.js version aliases to a list of numerical versions.

see: OpenJSF issue (#TODO: add link)
see: https://developers.redhat.com/blog/2021/02/10/add-standardized-support-information-to-your-node-js-modules

Dominant language
Shell
Stars
0
Forks
0
Avg merge
1d 3h
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from loopbackio/cicd

All issues in loopbackio/cicd

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.