open-index/open-npm huggingface dataset:
npm package: @novamoney/nova-pay
Description: A plugin to use Nova.Pay on Medusa.
Author: Nova.Money
Latest version: 1.1.1

<p align="center">
  <a href="https://nova.money">
    <img alt="Nova.Pay Logo" src="https://cdn.prod.website-files.com/67251f904799de91471deedf/672a520f1ab460471ae0969c_logo-purple.svg" width="200">
  </a>
</p>

<h1 align="center">
  Nova.Pay Medusa Plugin
</h1>

<p align="center">
  A <a href="https://www.medusajs.com">Medusa V2</a> plugin to integrate <a href="https://nova.money">Nova.Pay</a> into your store.
</p>

<p align="center">
  <a href="https://github.com/coyosoftware/nova-pay-medusa-plugin/blob/main/LICENSE">
    <img src="https://img.shields.io/badge/license-MIT-blue.svg" alt="License MIT" />
  </a>
</p>

## Features

- **Payment Providers**:
  - Credit Card (`nova-pay-credit-card`)
  - Pix (`nova-pay-pix`)
  - Boleto (`nova-pay-bank-slip`)
- **Product Sync**: Automatically syncs products to Nova.Pay whenever a product is created or updated in Medusa.

## Installation

Install the package via npm or yarn:

```bash
npm install @novamoney/nova-pay
# or
yarn add @novamoney/nova-pay
```

## Configuration

### Environment Variables

Add the following environment variables to your `.env` file:

```env
NOVA_PAY_API_KEY=your_api_key_here
NOVA_PAY_CART_PAGE_ID=your_cart_page_uuid_here
NOVA_PAY_SUBDOMAIN=your_nova_pay_subdomain_here
NOVA_PAY_VERBOSE=true      # Optional: enables sync logging
```

### Medusa Config

Enable the plugin in your `medusa-config.ts` file:

```typescript
// medusa-config.ts

module.exports = defineConfig({
  // ...
  plugins: [
    // ... other plugins
    {
      resolve: "@novamoney/nova-pay",
      options: {
        apiKey: process.env.NOVA_PAY_API_KEY,
        subdomain: process.env.NOVA_PAY_SUBDOMAIN
      },
    },
  ],
  // ...
  modules: [
    // ... other modules
    {
      resolve: "@medusajs/medusa/payment",
      options: {
        providers: [
          {
            resolve: "@novamoney/nova-pay/providers/payment",
            id: "nova-pay",
            options: {
              apiKey: process.env.NOVA_PAY_API_KEY,
              cartPageId: process.env.NOVA_PAY_CART_PAGE_ID,
              subdomain: process.env.NOVA_PAY_SUBDOMAIN
            }
          },
        ]
      }
    }
  ]
});
```

## Client-side Integration

When you initiate a payment using one of the Nova.Pay providers, the response will include a `link` in the `data` object of the payment session. You must redirect the customer to this URL to complete the payment.

### Example (Next.js Storefront)

```typescript
const handlePayment = async (paymentSession) => {
  if (paymentSession.data.link) {
    // Redirect to Nova.Pay checkout
    window.location.href = paymentSession.data.link;
  }
};
```

## License

Licensed under the [MIT License](LICENSE).
npm package: @novando/api-docs
Description: Node.js script to generate API documentation paths from templates
Latest version: 1.0.0

# API Docs Generator - Node.js Version

A Node.js conversion of the original Bash script for generating OpenAPI/Swagger documentation paths from templates.

## Prerequisites

- Node.js 20.0.0 or higher
- npm or yarn

## Installation

```bash
npm install
```

This installs the `js-yaml` dependency needed to parse YAML files.

## Usage

```bash
node api-docs-generator.js
```

Or if you installed it globally:

```bash
npm install -g .
api-docs-generator
```

## Features

- **Interactive CLI** - Prompts user for API details (method, path, title, domain, author)
- **Validation** - Validates HTTP methods, paths, and author codes
- **YAML Parsing** - Reads API version from OpenAPI spec files
- **Parameter Extraction** - Automatically extracts path and query parameters from URLs
- **Template Generation** - Generates API documentation files from templates with variable substitution
- **Author Tracking** - Maps author codes (daf, kam, muf, nov, sal) to full names

## Configuration Files

The script expects these paths to exist:

- **API Spec**: default to `resource/api-docs/v1/api-docs.yaml` (or user-provided path)

Output files are generated in: `{API_SPEC_DIR}/paths/{domain}/{method}-{operation}.yaml`

## Prompts

When run, the script will ask for:

1. **HTTP Method** - GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS, TRACE, CONNECT
2. **Path** - API path with optional path parameters in `{param}` format
3. **Title** - Human-readable title for the endpoint
4. **Domain** - Category/tag for the endpoint (e.g., "users", "products")
5. **Author** - Code for who created this using GitHub username

## Path Examples

Valid paths:
```
/users
/users/{userId}
/users/{userId}/posts?filter=active&sort=date
/products/{id}/reviews
```

Invalid paths:
```
users                    # Must start with /
/users/:id               # Use {id} instead of :id
/users?query=value       # Query string should be after path validation
```

## Path Parameter Handling

**Path Parameters** (in `{curly braces}`):
- Automatically extracted from path
- Marked as `required: true` in generated YAML
- Type set to `string`

**Query Parameters** (after `?`):
- Extracted from URL query string
- Marked as `in: query` in generated YAML
- Schema stub generated for manual completion

## Output

The script generates a YAML file with:

```yaml
/{path}:
  {method}:
    operationId: {operation_id}
    summary: {title}
    tags:
      - {domain}
    parameters: [...]
    responses:
      '200':
        description: Success
        content:
          application/json:
            schema:
              type: object
    x-author: {author}
    x-api-version: {version}
```

## Troubleshooting
**"API spec not found"**
- Provide the correct path to your OpenAPI specification file, relative to your caller location when prompted

**"Could not read info.version"**
- Ensure the API spec has a valid `info.version` field in YAML format

[Novando](https://localhost.com)
npm package: @novapo/medusajs-admin-ui
Description: <p align="center">   <a href="https://www.medusajs.com">     <img alt="Medusa" src="https://user-images.githubusercontent.com/7554214/153162406-bf8fd16f-aa98-4604-b87b-e13ab4baf604.png" width="100" />   </a> </p> <h1 align="center">   @medusajs/admi
Author: Kasper Kristensen
Latest version: 1.0.3

<p align="center">
  <a href="https://www.medusajs.com">
    <img alt="Medusa" src="https://user-images.githubusercontent.com/7554214/153162406-bf8fd16f-aa98-4604-b87b-e13ab4baf604.png" width="100" />
  </a>
</p>
<h1 align="center">
  @medusajs/admin-ui
</h1>

<h4 align="center">
  <a href="https://docs.medusajs.com">Documentation</a> |
  <a href="https://demo.medusajs.com/">Medusa Admin Demo</a> |
  <a href="https://www.medusajs.com">Website</a>
</h4>

<p align="center">
An open source composable commerce engine built for developers.
</p>
<p align="center">
  <a href="https://github.com/medusajs/medusa/blob/master/LICENSE">
    <img src="https://img.shields.io/badge/license-MIT-blue.svg" alt="Medusa is released under the MIT license." />
  </a>
  <a href="https://circleci.com/gh/medusajs/medusa">
    <img src="https://circleci.com/gh/medusajs/medusa.svg?style=shield" alt="Current CircleCI build status." />
  </a>
  <a href="https://github.com/medusajs/medusa/blob/master/CONTRIBUTING.md">
    <img src="https://img.shields.io/badge/PRs-welcome-brightgreen.svg?style=flat" alt="PRs welcome!" />
  </a>
    <a href="https://www.producthunt.com/posts/medusa"><img src="https://img.shields.io/badge/Product%20Hunt-%231%20Product%20of%20the%20Day-%23DA552E" alt="Product Hunt"></a>
  <a href="https://discord.gg/xpCwq3Kfn8">
    <img src="https://img.shields.io/badge/chat-on%20discord-7289DA.svg" alt="Discord Chat" />
  </a>
  <a href="https://twitter.com/intent/follow?screen_name=medusajs">
    <img src="https://img.shields.io/twitter/follow/medusajs.svg?label=Follow%20@medusajs" alt="Follow @medusajs" />
  </a>
</p>

## The Medusa Admin App. Included with the [`@medusajs/admin`](https://www.npmjs.com/package/@medusajs/admin) plugin. You shouldn't install this package separately.
npm package: @novara/plugin-vite
Description: Novara with SWC
Author: Jonatas Borges
Latest version: 1.0.1

# novara-plugin-vite [![npm](https://img.shields.io/npm/v/novara-plugin-vite)](https://www.npmjs.com/package/novara-plugin-vite)

Speed up your Vite dev server with [SWC](https://swc.rs/)

- ✅ A fast Fast Refresh (~20x faster than Babel)
- ✅ Enable [automatic JSX runtime](https://reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html)

## Installation

```sh
yarn add @novara/plugin-vite --dev
```
or
```sh
npm install @novara/plugin-vite --dev
```

## Usage

```ts
import { defineConfig } from "vite";
import novara from "@novara/plugin-vite";

export default defineConfig({
  plugins: [novara()],
});
```

## Caveats

This plugin is only used in development and aims to be kept simple to enable good performances and be transpiler agnostic. Here is the list of non-configurable options that impact runtime behaviour:

- [useDefineForClassFields](https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-7.html#the-usedefineforclassfields-flag-and-the-declare-property-modifier) is always activated, as this matches the current ECMAScript spec
- `jsx runtime` is always `automatic`
- In development:
  - esbuild is disabled, so the [esbuild configuration](https://vitejs.dev/config/shared-options.html#esbuild) has no effect
  - `target` is `es2020`
  - JS files are not transformed
  - tsconfig is not resolved, so properties other than the ones listed above behaves like TS defaults

## Changing the JSX import source

You can use the jsxImportSource option like this:

```ts
import { defineConfig } from "vite";
import novara from "@novara/plugin-vite";

export default defineConfig({
  plugins: [novara({ jsxImportSource: "@emotion/react" })],
});
```

## Consistent components exports

For React refresh to work correctly, your file should only export React components. The best explanation I've read is the one from the [Gatsby docs](https://www.gatsbyjs.com/docs/reference/local-development/fast-refresh/#how-it-works).

If an incompatible change in exports is found, the module will be invalidated and HMR will propagate. To make it easier to export simple constants alongside your component, the module is only invalidated when their value changes.

You can catch mistakes and get more detailed warning with this [eslint rule](https://github.com/ArnaudBarre/eslint-plugin-react-refresh).
npm package: @novaroma3162/novautils
Description: Utility functions for commonly used methods and operations
Author: Matthew Hemingway
Latest version: 0.1.2

# Utils

Node.js utilities for commonly used operations

## Installation

    `npm i -S @novaroma3162/novautils`

## Usage

    const utils = require('@novaroma3162/novautils');
    const result = utils.titleCase('i am number four');

Output should be `I Am Number Four`

## Tests

    `npm test`

## Contributing

In lieu of a formal style guide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code.
npm package: @novas/cli-utility
Description: NodeJS utilities and boilerplate for creating CLIs
Author: Cody Persinger
Latest version: 0.0.3

# @novas/cli-utility

NodeJS utilities and boilerplate for creating CLIs

## Installation

```sh
yarn add @novas/cli-utility got tar semver commander fast-fuzzy inquirer inquirer-autocomplete-prompt
```

## Functions

Modules are exported as both ESM and CJS

-   `checkPackageVersion` - Takes a package name and returns an object with metadata about the currently installed and latest published versions of the package.

```js
const {
	installedVersion,
	latestVersion,
	isInstalled,
	isLatest,
	isOutdated,
	isExperimental,
} = checkPackageVersion('create-next-app')
```

-   `downloadAndExtractGithub` - Takes a Github tree or blob URL including branch name and downloads and extracts the .tar.gz file to the cwd.

```js
try {
	await downloadAndExtractGithub(
		'https://github.com/codynova/eslint-config/tree/master'
	)
	console.log('success!')
} catch (error) {
	console.log(error)
}
```

-   `installDependenciesNpm` and `installDependenciesYarn` - Attempts to install dependencies with NPM or Yarn in the cwd.

```js
try {
	installDependenciesYarn()
	console.log('success!')
} catch (error) {
	console.log(error)
}
```

## Prior Art

-   [create-next-app](https://github.com/vercel/next.js/tree/master/packages/create-next-app)
npm package: @novas/eslint-config
Description: ESLint config for ESNext and TypeScript
Author: Cody Persinger
Latest version: 0.0.4

# @novas/eslint-config

ESLint config for ES2021 and TypeScript

## Installation

To use in your own custom configuration, install then extend this package in your ESLint config:

1. Install dependencies
```sh
yarn add --dev @novas/eslint-config @babel/core @babel/eslint-parser @babel/eslint-plugin @typescript-eslint/eslint-plugin @typescript-eslint/parser eslint eslint-config-prettier eslint-plugin-react eslint-plugin-react-hooks typescript 
```
Note: Due to the way ESLint `overrides` work, Typescript `devDependencies` are required regardless of whether you are using Typescript in your project.

2. Configure ESLint
```jsonc
// .eslintrc
{
    "extends": ["@novas/eslint-config"]
}
```
npm package: @novas/prettier-config
Description: Prettier config
Author: Cody Persinger
Latest version: 0.0.2

# @novas/prettier-config

Prettier config


## Installation

To use in your own custom configuration, install then extend this package in your Prettier config:

1. Install dependencies
```sh
yarn add --dev @novas/prettier-config prettier
```

2. Configure Prettier
```jsonc
// .prettierrc
"@novas/prettier-config"
```
npm package: @novas/styled-system
Description: Smaller faster rewrite of styled-system
Author: Cody Persinger
Latest version: 0.0.3

# @novas/styled-system

Smaller faster rewrite of styled-system

## Installation

```bash
yarn add @novas/styled-system
```

```jsx
import styled from 'styled-components'
import { styleFunction } from '@novas/styled-system'

const Box = styled.div`
	box-sizing: border-box;
	${styleFunction}
`
```

## Motivation

After using `styled-system` for some time, I found the style props to be the real strength of the library, rather than the theme system. This project is a faster and slimmer rewrite of the `styled-system` core runtime with less features (such as the object syntax for responsive styles).

## Changes from styled-system

-   Smaller (approx 5x)
-   Faster (approx 5x+ startup, equal runtime)
-   Zero dependencies
-   Removed all theme scales
-   Minor bugfixes (removed broken shorthand props like "bgImage")
-   Pre-compiled, no runtime extension
-   Only supports array responsive styles
-   Typescript from the ground up