open-index/open-npm huggingface dataset:
npm package: @steatopygous/correct-node
Description: CLI that checks whether the current Node version matches the one in package.json or a .nvmrc file.
Author: Harry Ohlsen
Latest version: 1.1.5

CLI that checks whether the current Node version matches the one in package.json or a .nvmrc file.

# Installation

npm install -g @steatopygous/correct-node

# Usage

Running

```
correct-node
```

will either exit with a zero status or exit with a status of -1 and print an error message.

The intended use is within scripts contained in the **package.json** of an application, to make sure that the current Node matches the one with which the application has been built and tested.  For example

```json
{
  "scripts": {
    "dev": "correct-node && webpack-dev-server"
  }
}
```

# What It Does

The current Node version is checked using the [semver](https://github.com/npm/node-semver) NPM module.

If the current folder contains a **package.json** file containing an **engines** specification for the node version, like

```json
{
  "engines": {
    "node": ">= 1.2.3 <4.5.6"
  }
}
```

that is used.  Otherwise, if there is a **.nvmrc** file it is used.

Having both is considered an error.
npm package: @steavebpi/angular-my-library
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 17.3.0.
Latest version: 0.0.2

# MyLibrary

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 17.3.0.

## Code scaffolding

Run `ng generate component component-name --project my-library` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project my-library`.
> Note: Don't forget to add `--project my-library` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build my-library` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build my-library`, go to the dist folder `cd dist/my-library` and run `npm publish`.

## Running unit tests

Run `ng test my-library` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI Overview and Command Reference](https://angular.io/cli) page.
npm package: @steavebpi/my-library
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 17.3.0.
Latest version: 1.0.3

# MyLibrary

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 17.3.0.

## Code scaffolding

Run `ng generate component component-name --project my-library` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project my-library`.
> Note: Don't forget to add `--project my-library` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build my-library` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build my-library`, go to the dist folder `cd dist/my-library` and run `npm publish`.

## Running unit tests

Run `ng test my-library` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI Overview and Command Reference](https://angular.io/cli) page.