open-index/open-npm huggingface dataset:
npm package: @netatwork/check-npm-dependencies
Description: A linter for bundled npm dependencies
Author: Net at Work GmbH
Latest version: 4.0.0

# @netatwork/check-npm-dependencies
A linter for package locks.

## Installation
```bash
npm i -D @netatwork/check-npm-dependencies
```

## Configuration
```js
// package.json
{
  ...
  "nawCheckNpmDependencies": {
    "extends": "./some-shared-config.json",
    "noDuplicates": [
      "@example/*"
    ],
    "sameVersions": [
      "@example/*",
      [
        "example-a-*",
        "example-b"
      ]
    ]
  }
}
```
+ **nawCheckNpmDependencies** `<Config>` - Can be a path to load the config from or an object with the following options:
  + **extends** `<string>` - A path to load a config from to extend.
  + **noDuplicates** `<string[]>` - An array of package name patterns to check for duplicates.
    + In the example above, all packages within the `@example` scope are checked for duplicates.
  + **sameVersions** `<(string | string[])[]>` - An array of patterns or pattern groups to ensure that all packages within a group have the same versions.
    + In the example above, all packages within the `@example` scope are checked for the same version and `example-a-*` and `example-b` are checked for the same version.

## Usage
```bash
# Run via npx:
npx naw-check-npm-dependencies [...args]
```
```js
// Or add to your package.json:
{
  "scripts": {
    "test": "naw-check-npm-dependencies ..."
  }
}
```

+ `--context | -c <path>` - The path at which to look for a `package.json` and `package-lock.json`.
npm package: @netautomate/plugin-netorca
Description: Welcome to the netorca plugin!
Latest version: 0.1.0

# netorca

Welcome to the netorca plugin!

_This plugin was created through the Backstage CLI_

## Getting started

Your plugin has been added to the example app in this repository, meaning you'll be able to access it by running `yarn start` in the root directory, and then navigating to [/netorca](http://localhost:3000/netorca).

You can also serve the plugin in isolation by running `yarn start` in the plugin directory.
This method of serving the plugin provides quicker iteration speed and a faster startup and hot reloads.
It is only meant for local development, and the setup for it can be found inside the [/dev](./dev) directory.
npm package: @netautomate/plugin-netorca-backend
Description: This plugin backend was templated using the Backstage CLI. You should replace this text with a description of your plugin backend.
Latest version: 0.1.0

# netorca

This plugin backend was templated using the Backstage CLI. You should replace this text with a description of your plugin backend.

## Installation

This plugin is installed via the `@netautomate/plugin-netorca-backend` package. To install it to your backend package, run the following command:

```bash
# From your root directory
yarn --cwd packages/backend add @netautomate/plugin-netorca-backend
```

Then add the plugin to your backend in `packages/backend/src/index.ts`:

```ts
const backend = createBackend();
// ...
backend.add(import('@netautomate/plugin-netorca-backend'));
```

## Development

This plugin backend can be started in a standalone mode from directly in this
package with `yarn start`. It is a limited setup that is most convenient when
developing the plugin backend itself.

If you want to run the entire project, including the frontend, run `yarn dev` from the root directory.
npm package: @netautomate/plugin-scaffolder-backend-module-netorca-get-serviceitems
Description: The netorca-get-serviceitems module for @backstage/plugin-scaffolder-backend
Latest version: 0.1.0

# @netautomate/plugin-scaffolder-backend-module-netorca-get-serviceitems

The netorca-get-serviceitems module for [@backstage/plugin-scaffolder-backend](https://www.npmjs.com/package/@backstage/plugin-scaffolder-backend).

_This plugin was created through the Backstage CLI_