open-index/open-npm huggingface dataset:
npm package: @nas-veridid/workflow-parser
Description: Workflow Parser is a TypeScript Node.js module for parsing and managing workflow definitions in a PostgreSQL database.
Author: Nas Til
Latest version: 0.3.3

# workflow-parser
Workflow Parser is a TypeScript Node.js module for parsing and managing workflow definitions in a PostgreSQL database. It retrieves workflows and instances, parses data, and handles state transitions. Ideal for managing complex workflows and integrating action-menu features.

## Key Features

- **Database Integration:** Connects to a PostgreSQL database to store and manage workflow definitions and instances.
- **Workflow Management:** Supports defining workflows with states, transitions, actions, and display data.
- **State Parsing:** Parses workflows to handle state transitions based on predefined conditions.
- **Modular Design:** Can be easily integrated into different applications, including NestJS projects.

## development

```sh
npm run build
```
and  

Must be logged into npm

```sh
npm publish 
```

## Installation

```sh
npm install @digicred/workflow-parser
```
or 

```sh
yarn add @digicred/workflow-parser
```
npm package: @nasa-gcn/architect-functions-search
Description: Architect functions for OpenSearch
Latest version: 1.0.1

[![npm](https://img.shields.io/npm/v/@nasa-gcn/architect-functions-search)](https://www.npmjs.com/package/@nasa-gcn/architect-functions-search)

# Architect functions for OpenSearch / ElasticSearch

This package provides an automatically configured [client for OpenSearch](https://opensearch.org/docs/latest/clients/javascript/index/) in an [Architect](https://arc.codes/) application.

Pair this package with [@nasa-gcn/architect-plugin-search](https://github.com/nasa-gcn/architect-plugin-search), a [plugin](https://arc.codes/docs/en/guides/plugins/overview) that adds [Amazon OpenSearch](https://aws.amazon.com/opensearch-service/) to your application.

## To install

```
npm i @nasa-gcn/architect-functions-search
```
npm package: @nasa-gcn/architect-plugin-dynamodb-local
Description: Architect plugin for a local DynamoDB instance
Latest version: 0.1.2

# Architect plugin for Local DynamoDB Docker

This is a plugin for a local DynamoDB instance using Docker.

When you are using Architect's sandbox mode, the plugin starts a Docker container running the [`amazon/dynamodb-local`](https://hub.docker.com/r/amazon/dynamodb-local) image.

If you have defined a `@tables-streams` section in your `app.arc` file, the respective streams will be enabled and their configured lambdas automatically triggered.

## Prerequisites

- Docker installed and running on your system.
- Node.js (if this project is built as a Node.js tool).

## Usage

1. Install this package using npm:

   ```
   npm install -D @nasa-gcn/architect-plugin-dynamodb-local
   ```

2. In your `.env` add the following:

   ```
   ARC_TABLES_PORT=8000
   ARC_DB_EXTERNAL=true
   ```

3. Add the following to your project's `app.arc` configuration file:

   ```
   @plugins
   nasa-gcn/architect-plugin-dynamodb-local
   ```

4. Seeding the database (optional):

   ```
   @dynamodb-local
   seedFile your-seed-file.json
   ```

If you want to utilize the @tables-streams, include a json formatted seedFile. The database will be seeded automatically during initialization. This will happen **BEFORE** Architect's built-in seeding step. By default, Architect will look for a file named `sandbox-seed.json` or `sandbox-seed.js` to seed the database. If you use this feature name the file differently, otherwise this plugin will skip the file seeding. To easily switch from using the built-in seed function, you can simply rename your existing `sandbox-seed.[js|json]` file and pass that as an argument to the plugin.

### Seed File Format

The seedFile should be a JSON file where the keys are the table names and the values are the list of items to be added. Example:

```
{
  "table1": [
    {
      "someProperty":"some value",
      ...
    },
    {
      ...
    }
  ],
  "table2": [
    ...
  ]
}
```
npm package: @nasa-gcn/architect-plugin-dynamodb-local-streams
Description: Architect plugin for Local DynamoDB Streams
Latest version: 0.0.3

# Architect plugin for Local DynamoDB Streams

This is a plugin for invoking stream functions defined in the `@tables-streams` pragma alongside a local DynamoDB instance.

When using Architect's sandbox mode, the plugin will consistently poll the local database for events with records. If records are found, it will invoke the function associated with the table.

## Prerequisites

- [@nasa-gcn/architect-plugin-dynamodb-local](https://github.com/nasa-gcn/architect-plugin-dynamodb-local) or another means of running a local dynamodb instance
- Node.js (if this project is built as a Node.js tool).

## Usage

1. Install this package using npm:

```
npm i @nasa-gcn/architect-plugin-dynamodb-local-streams
```

2. Add the following to your project's `app.arc` configuration file:

```
@plugins
nasa-gcn/architect-plugin-dynamodb-local-streams
```

## Known issues

There is an issue with the Docker image of DynamoDB local that causes a TrimmedDataAccessException error to be thrown on the first read. This problem lies deeper within DynamoDB and is out of the scope of this plugin. To handle this issue, there is a reset function that will trigger automatically. In practice, this means that the 1st invocation will fail (you will see a logged `TrimmedDataAccessException` message in your console), but the following invocations will work successfully.
npm package: @nasa-gcn/architect-plugin-tracing
Description: Architect plugin for tracing Lambdas with OpenTelemetry and shipping results to AWS X-Ray
Latest version: 1.1.0

[![npm](https://img.shields.io/npm/v/@nasa-gcn/architect-plugin-tracing)](https://www.npmjs.com/package/@nasa-gcn/architect-plugin-tracing)

# Architect plugin for OpenTelemetry + AWS X-Ray

This is a [plugin](https://arc.codes/docs/en/guides/plugins/overview) for [Architect](https://arc.codes/) that automatically instruments your Node.js Lambdas with [OpenTelemetry](https://opentelemetry.io) and sends tracing data and metrics to [AWS X-Ray](https://aws.amazon.com/xray/).

It adds the [AWS Distro for OpenTelemetry Lambda layer](https://aws-otel.github.io/docs/getting-started/lambda) to all of your Lambdas for which you have enabled tracing.

## Usage

1.  Install this package using npm:

        npm i -D @nasa-gcn/architect-plugin-tracing

2.  Add the following to your project's `app.arc` configuration file:

        @plugins
        nasa-gcn/architect-plugin-tracing

3.  Enable tracing for all Lambdas by adding the folllowing lines to your `app.arc` file, or for [an individual Lambda](https://arc.codes/docs/en/reference/configuration/function-config) by adding it to the Lambda's `config.arc` file:

        @aws
        tracing true

4.  Optionally, you can inject additional OpenTelemetry configuration into a Lambda by adding a file called `tracing.js` to its source directory. Here is an example that adds [instrumentation for the Remix web framework](https://www.npmjs.com/package/opentelemetry-instrumentation-remix):

        ```js
        global.configureInstrumentations = () => {
          const { DnsInstrumentation } = require('@opentelemetry/instrumentation-dns')
          const { HttpInstrumentation } = require('@opentelemetry/instrumentation-http')
          const { NetInstrumentation } = require('@opentelemetry/instrumentation-net')
          const {
            RemixInstrumentation,
          } = require('opentelemetry-instrumentation-remix')

          return [
            new DnsInstrumentation(),
            new HttpInstrumentation(),
            new NetInstrumentation(),
            new RemixInstrumentation(),
          ]
        }
        ```
npm package: @nasa-gcn/architect-plugin-utils
Description: Architect plugin utilities
Latest version: 0.4.0

[![npm](https://img.shields.io/npm/v/@nasa-gcn/architect-plugin-utils)](https://www.npmjs.com/package/@nasa-gcn/architect-plugin-utils)

# Architect plugin utilities

This provides miscellaneous utilities for Architect plugins which are shared between https://github.com/nasa-gcn/architect-plugin-search and https://github.com/nasa-gcn/architect-plugin-dynamodb-local.
npm package: @nasa-gcn/dynamodb-autoincrement
Description: Use optimistic locking to put DynamoDB records with auto-incrementing attributes
Latest version: 2.2.1

[![npm](https://img.shields.io/npm/v/@nasa-gcn/dynamodb-autoincrement)](https://www.npmjs.com/package/@nasa-gcn/dynamodb-autoincrement)
[![codecov](https://codecov.io/gh/nasa-gcn/dynamodb-autoincrement/branch/main/graph/badge.svg?token=C84AQR8UAS)](https://codecov.io/gh/nasa-gcn/dynamodb-autoincrement)

# dynamodb-autoincrement

Use optimistic locking to put DynamoDB records with auto-incrementing attributes. Inspired by:

- https://aws.amazon.com/blogs/aws/new-amazon-dynamodb-transactions/
- https://bitesizedserverless.com/bite/reliable-auto-increments-in-dynamodb/
npm package: @nasa-gcn/eslint-config-gitignore
Description: ESLint plugin to ignore files listed in .gitignore
Latest version: 1.0.0

[![NPM Version](https://img.shields.io/npm/v/%40nasa-gcn%2Feslint-config-gitignore)](https://www.npmjs.com/package/@nasa-gcn/eslint-config-gitignore)

# eslint-plugin-gitignore

ESLint plugin to ignore files listed in .gitignore

## Installation

You'll first need to install [ESLint](https://eslint.org/):

```sh
npm i eslint --save-dev
```

Next, install `eslint-plugin-gitignore`:

```sh
npm install @nasa-gcn/eslint-config-gitignore --save-dev
```

## Usage

Add to your [ESLint configuration file](https://eslint.org/docs/latest/use/configure/configuration-files#configuration-file) like this:

```js
// eslint.config.mjs
import { defineConfig } from "eslint/config";
import eslintConfigGitignore from "@nasa-gcn/eslint-config-gitignore";

export default defineConfig(
  eslintConfigGitignore,
);
```
npm package: @nasa-gcn/rcfiles
Description: Shared ESLint, Prettier, and lint-staged configs for https://gcn.nasa.gov projects
Latest version: 0.1.0

# @nasa-gcn/rcfiles

This package provides shared ESLint, Prettier, and lint-staged configs for https://gcn.nasa.gov projects.

To use, install in your project by running this command:

    $ npm install --save-dev @nasa-gcn/rcfiles

Then, create three files with the following contents inside your project:

- eslint.config.mjs

      export { default } from '@nasa-gcn/rcfiles/eslint.config.js'

- lint-staged.config.mjs

      export { default } from '@nasa-gcn/rcfiles/lint-staged.config.js'

- prettier.config.mjs

      export { default } from '@nasa-gcn/rcfiles/prettier.config.js'