open-index/open-npm huggingface dataset:
npm package: @lambdacurry/medusa-ziptax-plugin
Description: A plugin for using tax rates from ziptax
Author: Adrien de Peretti
Latest version: 0.1.4

<!--lint disable awesome-list-item-->
<div align="center">
  <p align="center">
    <img alt="Medusa" src="https://uploads-ssl.webflow.com/61fba9f6deac297b7b22017d/62000006ce573a706c92546c_logo.svg" width="200" />
  </p>
  <h1>Plugin starter (Typescript)</h1>
  <p>Start to write your own plugin as quick as possible</p>
    
  <a href="https://github.com/adrien2p/awesome-medusajs">
      <img src="https://awesome.re/badge.svg" alt="Awesome">
  </a>
</div>

# Getting started

Installation

```bash
git clone git@github.com:adrien2p/medusa-plugin-starter-ts.git
```

# Usage

## Api

### Admin routes

Those routes will automatically be attached by medusa to the `admin` path.

### Store routes

Those routes will automatically be attached by medusa to the `store` path.

### Custom routes

All those routes are added in the main router and you have to manage them.

## Models/Migrations

Those models will be attach to the manager and included into the medusa container.
The migrations will be applied automatically.

## Subscribers

It acts like a service but its main purpose is to extends core flow depending on the
events you want to listen to.

## Services

Those services will be automatically added to the medusa container and will be available
in any other service through the constructor injection.

## Loaders

Those will be applied during the loading and allow you to register custom components
to the container to be accessible later on.

# Deployment

Once your plugin is done. 

```bash
npm run build && npm version && npm publish
```

You can now install it into your project file `medusa-config`.
npm package: @lambdacurry/tsoa
Description: Build swagger-compliant REST APIs using TypeScript and Node
Author: Derek Wene
Latest version: 5.1.2

<div align="center">
  <a href="https://tsoa-community.github.io/docs/" target="blank">
    <h1>tsoa</h1>
  </a>
Pronounced so·uh

OpenAPI-compliant REST APIs using TypeScript and Node

![build status](https://github.com/lukeautry/tsoa/actions/workflows/runTestsOnPush.yml/badge.svg)
[![npm version](https://img.shields.io/npm/v/tsoa/latest)](https://www.npmjs.com/package/tsoa)

</div>

## Goal

- TypeScript controllers and models as the single source of truth for your API
- A valid OpenAPI (formerly Swagger) spec (2.0 or 3.0 if you choose 😍) is generated from your controllers and models, including:
  - Paths (e.g. GET /users)
  - Definitions based on TypeScript interfaces (models)
  - Parameters/model properties marked as required or optional based on TypeScript (e.g. myProperty?: string is optional in the OpenAPI spec)
  - jsDoc supported for object descriptions (most other metadata can be inferred from TypeScript types)
- Routes are generated for middleware of choice
  - Express, Hapi, and Koa currently supported, other middleware can be supported using a simple handlebars template
  - Validate request payloads

## Philosophy

- Rely on TypeScript type annotations to generate API metadata if possible
- If regular type annotations aren't an appropriate way to express metadata, use decorators
- Use jsdoc for pure text metadata (e.g. endpoint descriptions)
- Minimize boilerplate
- Models are best represented by interfaces (pure data structures), but can also be represented by classes
- Runtime validation of tsoa should behave as closely as possible to the specifications that the generated OpenAPI 2/3 schema describes. Any differences in validation logic are clarified by logging warnings during the generation of the OpenAPI Specification (OAS) and/or the routes.
  - Please note that by enabling OpenAPI 3 you minimize the chances of divergent validation logic since OpenAPI 3 has a more expressive schema syntax.

## Getting Started

- [Documentation](https://tsoa-community.github.io/docs/)
- [API Reference](https://tsoa-community.github.io/reference/)
- [Getting started guide](https://tsoa-community.github.io/docs/getting-started)

## Examples

Check out the [guides](https://tsoa-community.github.io/docs/getting-started)

See example controllers in [the tests](tests/fixtures/controllers)

See example models in [the tests](tests/fixtures/testModel.ts)

## Help wanted

### Contributing code

To contribute (via a PR), please first see the [Contributing Guide](https://github.com/lukeautry/tsoa/tree/master/docs/CONTRIBUTING.md)

### Becoming a maintainer

tsoa wants additional maintainers! The library has increased in popularity and has quite a lot of pull requests and issues. [Please post in this issue](https://github.com/lukeautry/tsoa/issues/236) if you're willing to take on the role of a maintainer.
npm package: @lambdacurry/vercel-remix
Description: Isomorphic runtime + adapter for Remix on Vercel
Latest version: 2.10.3

# Welcome to Remix!

[Remix](https://remix.run) is a web framework that helps you build better websites with React.

To get started, open a new shell and run:

```sh
npx create-remix@latest
```

Then follow the prompts you see in your terminal.

For more information about Remix, [visit remix.run](https://remix.run)!
npm package: @lambdadesign/essentials-tsconfig
Description: A collection of strict reusable TypeScript configurations for various project types to help the enforcement of best practices and consistency across projects.
Latest version: 0.0.15

<!-- TITLE -->
# @lambdadesign/essentials-tsconfig

<!-- LOGO -->
<div align="center" style="text-align: center;">
  <a href="">
    <img
    src="./resources/images/banner.png"
    alt="@lambdadesign/essentials-tsconfig banner"
    style="width: 100%; border:none;"
    />
  </a>
</div>

This directory contains strict reusable TypeScript configurations for various project types to help the enforcement of best practices and consistency across TypeScript projects.

<!-- BADGES -->
[![Version](https://img.shields.io/npm/v/%40lambdadesign%2Fessentials-tsconfig?label=Version&labelColor=454E57&color=59D73A "Version")](https://www.npmjs.com/package/@lambdadesign/essentials-tsconfig)
[![License MIT](./resources/images/badges/license.svg "License MIT")](./LICENSE)
[![lambda.design](../../../../resources/images/badges/lambdadesign.svg "lambda.design")](https://lambda.design)
<!--
[![NPM downloads](https://img.shields.io/npm/dw/@lambdadesign/essentials-tsconfig
 "NPM downloads")](https://www.npmjs.com/package/@lambdadesign/essentials-tsconfig)
[![NPM collaborators](https://img.shields.io/npm/collaborators/@lambdadesign/essentials-tsconfig
 "NPM collaborators")](https://www.npmjs.com/package/@lambdadesign/essentials-tsconfig)
[![NPM last update](https://img.shields.io/npm/last-update/@lambdadesign/essentials-tsconfig
 "NPM last update")](https://www.npmjs.com/package/@lambdadesign/essentials-tsconfig)
 [![NPM unpacked size](https://img.shields.io/npm/unpacked-size/@lambdadesign/essentials-tsconfig
 "NPM unpacked size")](https://www.npmjs.com/package/@lambdadesign/essentials-tsconfig)
 -->
---

Configs to have:
- node modern config (default)
- node legacy config
- bun config https://bun.com/docs/runtime/typescript
- node bundler
- frontend bundler
- frontend bundler preact
- frontend bundler react-native
- frontend bundler webworker


TODO:
- Add tests for each configs
- Review or delete comments
npm package: @lambdalabs/base-generator
Description: A yeoman base class used by labs generators
Author: Lambda Labs
Latest version: 1.0.3

# Lambda Labs Generator Base class

This base class has common functions used in multiple generators.

## Using the base class

When creating a new app generator or sub-generator start off with this
template.

``` javascript
const BaseGenerator = require('@lambdalabs/base-generator');

module.exports = class extends BaseGenerator {
  constructor(args, opts) {
    super(args, opts);
  }
}
```
npm package: @lambdalabs/labs
Description: The Labs scaffolding
Author: Lambda Labs
Latest version: 0.1.14

# Labs wrapper for Yeoman

This wrapper of yeoman simply allows the use of `labs` in place of the common
use of `yo`

## Installation

> The project has not yet been deployed to <npmjs.com> yet.

`npm i -g @lambdalabs/labs`

This will install the main cli wrapper along with all Labs generators as
dependancies.

## Usage

The `labs` cli command is just a wrapper to the [yeoman](https://yeoman.io/learning/index.html)
`yo` command.

## Examples

- Run the SPA generator (base react single page app starter)
  
  `labs @lambdalabs/spa project-name`

- Run the Node API generator (base node express api starter)
  
  `labs @lambdalabs/api project-name`

## Generators

- [SPA React](https://www.npmjs.com/package/@lambdalabs/generator-spa)
- [Node API](https://www.npmjs.com/package/@lambdalabs/generator-api)

## publish npmjs package

- update package.json version
- add a git tag with the version number `git tag v0.9.30 -m "release note"`
- push repo and tags `git push && git push --tags`

## Development setup

To develop locally it will be easiest to link the `labs` command and any generators being developed using npm.

1. link the generator in the labs-yo project folder.

    1. Go to the cloned and npm-installed project folder
    2. `npm link`
    3. Cd back to this `labs-yo` folder
    4. `npm link "name-of-package"`
    5. Example: `npm link "generator-spa`

2. link this project to the global npm commands.

    `npm link`

    The `labs` command is now globally available.

    `labs --help` should render the `yo` command options.
npm package: @lambdalang/lambda
Description: A language
Author: Kaguyasen
Latest version: 1.1.1

![Lambda](https://media.discordapp.net/attachments/665390060392284174/670948190081515530/lambda.png?width=300&height=300)

# Lambda
Lambda is an esoteric language oriented highly around [Texas Instruments](https://lmgtfy.com/?q=texas+instruments) brand calculators, holding similar syntax to using equations in them. This language is **highly** work in progress, so many things can potentially be changed and added to it at a whole. 

If you wish to contribute to the Lambda specifications/design, then we have an [entire repository](https://github.com/lambdalng/lambda-spec) with information on how to contribute to what functions are what.

### Installation
As this language is still in in its **very alpha** phase, you should preferrably download development updates over from GitHub.
```
npm i -g lambdalng/lambda
```

However, you're still able to download it in NPM, but it gets updated slower in favor of development, unless breaking changes are necessary.
```
npm i -g @lambdalang/lambda
```

### Usage
This language cannot be directly compiled to basic JavaScript yet, but can be used via CLI. You are perfectly able to use it as if it were an API, but it's undocumented, as it's unsupported for the time being.
```
lambda ./path/to/script.lam
```

### Contributions
Contributions are allowed, but it would be best for you to make note of it with the lead maintainers before you contribute huge amounts of code. This project was primarily made for fun, although improvements to make this a true project are undoubtedly allowed. We as a team would like to give this language major purpose, rather than being merely limited to basic TI syntax.

### Links
- [NPM](https://www.npmjs.com/package/@lambdalang/lambda)
- [Language Github](https://github.com/lambdalng/lambda)
- [Maintainers/Organization](https://github.com/lambdalng)
- [Language Specifications](https://github.com/lambdalng/lambda-spec)
npm package: @lambdalf-dev/ethereum-contracts
Description: A set of implementations of common Ethereum contracts
Author: Lambdalf the White
Latest version: 3.2.1

# Ethereum Contracts

This project is an attempt to create a more efficient implementation of the common interface IERC721 compared to Open Zeppelin's implementation.

## What's Inside

- [Forge](https://github.com/foundry-rs/foundry/blob/master/forge): compile, test, fuzz, format, and deploy smart
  contracts
- [Forge Std](https://github.com/foundry-rs/forge-std): collection of helpful contracts and utilities for testing

## Installation

Foundry typically uses git submodules to manage dependencies, but this template uses Node.js packages because
[submodules don't scale](https://twitter.com/PaulRBerg/status/1736695487057531328).

This is how to install dependencies:

1. Install the dependency using your preferred package manager, e.g. `yarn install dependency-name`
   - Use this syntax to install from GitHub: `yarn install github:username/repo-name`
2. Add a remapping for the dependency in [remappings.txt](./remappings.txt), e.g.
   `dependency-name=node_modules/dependency-name`

## Usage

### Build/Compile

Build the contracts:

- ```yarn build```
- ```forge build```
- ```forge compile```

### Clean

Delete the build artifacts and cache directories:

- ```yarn clean```
- ```forge clean```

### Coverage

Get a test coverage report:

- ```yarn coverage```
- ```forge coverage```

### Gas Report

Get a gas report:

- ```yarn gas```
- ```forge test --gas-report```

### Lint

Format the contracts:

- ```yarn lint```
- ```forge fmt check```

### Test

Run all tests:

- ```yarn test```
- ```forge test```

Run all tests with verbose output:

- ```yarn test:verbose```
- ```forge test -vvvv```

Run all unit tests (test name starts with "test_unit_"):

- ```yarn test:unit```
- ```forge test --mt test_unit_```

Run all fuzz tests (test name starts with "test_fuzz_"):

- ```yarn test:fuzz```
- ```forge test --mt test_fuzz_```

Run all edge tests (test name starts with "test_edge_"):

- ```yarn test:edge```
- ```forge test --mt test_edge_```
npm package: @lambdalisue/errorutil
Description: [![JSR](https://jsr.io/badges/@lambdalisue/errorutil)](https://jsr.io/@lambdalisue/errorutil) [![Test](https://github.com/lambdalisue/deno-errorutil/workflows/Test/badge.svg)](https://github.com/lambdalisue/deno-errorutil/actions?query=workflow%3ATest) [!
Author: Alisue
Latest version: 1.0.2

# errorutil

[![JSR](https://jsr.io/badges/@lambdalisue/errorutil)](https://jsr.io/@lambdalisue/errorutil)
[![Test](https://github.com/lambdalisue/deno-errorutil/workflows/Test/badge.svg)](https://github.com/lambdalisue/deno-errorutil/actions?query=workflow%3ATest)
[![codecov](https://codecov.io/gh/lambdalisue/deno-errorutil/graph/badge.svg?token=O0cA5Xj5la)](https://codecov.io/gh/lambdalisue/deno-errorutil)

A utility pack for handling error.

[deno]: https://deno.land/

> [!WARNING]
>
> The package on [deno.land] and [npm] is deprecated. Use the package on
> [jsr.io] instead.
>
> ```
> $ deno add @lambdalisue/errorutil
> $ npx jsr add @lambdalisue/errorutil
> ```

[deno.land]: https://deno.land/x/errorutil
[npm]: https://www.npmjs.com/package/@lambdalisue/errorutil
[jsr.io]: https://jsr.io/@lambdalisue/errorutil

## License

The code follows MIT license written in [LICENSE](./LICENSE). Contributors need
to agree that any modifications sent in this repository follow the license.
npm package: @lambdaschool/generator-prismatopia
Description: Yeoman generator for Prismatopia
Author: Bernie Durfee
Latest version: 0.1.2

# Prismayopia

> Yeoman generator for Prismatopia

[![NPM version][npm-image]][npm-url]
[![Dependency Status][daviddm-image]][daviddm-url]
[![Maintainability](https://api.codeclimate.com/v1/badges/d3970d4328eeb48ad49b/maintainability)](https://codeclimate.com/github/Lambda-School-Labs/generator-prismatopia/maintainability)
[![Test Coverage](https://api.codeclimate.com/v1/badges/d3970d4328eeb48ad49b/test_coverage)](https://codeclimate.com/github/Lambda-School-Labs/generator-prismatopia/test_coverage)

## Install Yeoman and the Prismatopia generator

```bash
yarn global add yo
yarn global add @lambdaschool/generator-prismatopia
```

## Generate a Prismatopia project

```bash
yo prismatopia
```

## License

MIT © [Lambda School](https://lambdaschool.com)

[npm-image]: https://badge.fury.io/js/%40lambdaschool%2Fgenerator-prismatopia.svg
[npm-url]: https://www.npmjs.com/package/@lambdaschool/generator-prismatopia
[daviddm-image]: https://david-dm.org/Lambda-School-Labs/generator-prismatopia.svg?theme=shields.io
[daviddm-url]: https://david-dm.org/Lambda-School-Labs/generator-prismatopia
npm package: @lambdatest/demo-sdk
Description: Demo Playwright SDK for CI Testing
Author: Demo Author
Latest version: 1.0.0

# LambdaTest Demo SDK

A demo SDK for testing CI/CD pipeline with npm package publishing.

## Installation

```bash
npm install @lambdatest/demo-sdk
```

## Usage

### As a CLI tool

```bash
# Initialize the SDK
npx demo-playwright-sdk init

# Run a test with configuration
npx demo-playwright-sdk run --config ./test-config.json
```

### As a library

```javascript
const DemoSDK = require('@lambdatest/demo-sdk');

async function runTest() {
  const sdk = new DemoSDK({
    debug: true
  });

  await sdk.initialize();
  
  const results = await sdk.runTest({
    testName: 'demo-test',
    parameters: {
      // your test parameters
    }
  });

  const report = await sdk.generateReport(results);
  console.log(report);
}

runTest();
```

## Configuration

The SDK accepts the following configuration options:

- `debug` (boolean): Enable debug logging
- `logLevel` (string): Set logging level (default: 'info')

## Development

```bash
# Install dependencies
npm install

# Build the SDK
npm run build

# Build for development (without obfuscation)
npm run build:dev

# Create a package
npm run pack
```

## License

MIT