open-index/open-npm huggingface dataset:
npm package: @shoplyjs/admin-ui
Description: This is the administration interface for Vendure.
Latest version: 2.3.4

# Vendure Admin UI

This is the administration interface for Vendure.

It is an Angular application built with the Angular CLI.

The UI is powered by the [Clarity Design System](https://clarity.design).

## Structure

### Library

The Admin UI is structured as an Angular library conforming to the [ng-packagr format](https://github.com/ng-packagr/ng-packagr). This library is what is published to npm as `@vendure/admin-ui`. The library consists
of a set of modules which are accessible from consuming applications as sub-packages:

* `@vendure/admin-ui/core`
* `@vendure/admin-ui/catalog`
* `@vendure/admin-ui/orders`

etc. These library packages are located at [./src/lib](./src/lib)

When built with `npm run build`, the output will be located in the `./package` sub directory. This is also the root of the published npm package.

### Application

In addition to the library, there is also a full application located at [./src/app](./src/app). This application is used both during development of the Admin UI, and also as the "default" Admin UI without any UI extensions, as provided as the default by the [admin-ui-plugin](../admin-ui-plugin).

## Localization

Localization of UI strings is handled by [ngx-translate](http://www.ngx-translate.com/). The translation strings should use the [ICU MessageFormat](http://userguide.icu-project.org/formatparse/messages).

Translation keys are automatically extracted by running:
```
npm run extract-translations
```
This scan the source files for any translation keys, and add them to each of the translation files located in [`./src/lib/static/i18n-messages/`](./src/lib/static/i18n-messages/).

A report is generated for each language detailing what percentage of the translation tokens are translated into that language:

```text
Extracting translation tokens for "src\lib\static\i18n-messages\de.json"
de: 592 of 650 tokens translated (91%)
```

This report data is also saved to the [i18n-coverage.json](./i18n-coverage.json) file.

To add support for a new language, create a new empty json file (`{}`) in the `i18n-messages` directory named `<languageCode>.json`, where `languageCode` is one of the supported codes as given in the [LanguageCode enum type](../core/src/api/schema/common/language-code.graphql), then run `npm run extract-translations`

To verify localization changes add `<languageCode>.json` to `./src/lib/static/vendure-ui-config.json` in the array `availableLanguages`. This will make the localization available in Admin UI development mode using `npm run start`
npm package: @shoplyjs/admin-ui-plugin
Description: `npm install @vendure/admin-ui-plugin`
Latest version: 2.3.4

# Vendure AdminUiPlugin

`npm install @vendure/admin-ui-plugin`

For documentation, see [docs.vendure.io/reference/core-plugins/admin-ui-plugin/](https://docs.vendure.io/reference/core-plugins/admin-ui-plugin/)
npm package: @shoplyjs/asset-server-plugin
Description: The `AssetServerPlugin` serves assets (images and other files) from the local file system. It can also perform on-the-fly image transformations and caches the results for subsequent calls.
Latest version: 2.3.5

# Vendure AssetServerPlugin

The `AssetServerPlugin` serves assets (images and other files) from the local file system. It can also perform on-the-fly image transformations and caches the results for subsequent calls.

`npm install @vendure/asset-server-plugin`

For documentation, see [docs.vendure.io/reference/core-plugins/asset-server-plugin/](https://docs.vendure.io/reference/core-plugins/asset-server-plugin/)
npm package: @shoplyjs/common
Description: This package contains a set of common utility functions and TypeScript types used by multiple Vendure packages. It is not intended to be directly depended upon by an end-user project.
Latest version: 2.3.7

# @vendure/common

This package contains a set of common utility functions and TypeScript types used by multiple Vendure packages. It is not intended to be directly depended upon by an end-user project.
npm package: @shoplyjs/core
Description: A modern, headless ecommerce framework
Latest version: 2.3.4

# Vendure

A headless [GraphQL](https://graphql.org/) ecommerce framework built on [Node.js](https://nodejs.org) with [Nest](https://nestjs.com/) with [TypeScript](http://www.typescriptlang.org/).

```bash
$ npm install @vendure/core
```

### [www.vendure.io](https://www.vendure.io/)

See the [Getting Started](https://www.vendure.io/docs/getting-started/) guide for instructions on use.
npm package: @shoplyjs/create
Description: A CLI tool for rapidly scaffolding a new Vendure server application. Heavily inspired by [create-react-app](https://github.com/facebook/create-react-app).
Latest version: 2.3.4

# Vendure Create

A CLI tool for rapidly scaffolding a new Vendure server application. Heavily inspired by [create-react-app](https://github.com/facebook/create-react-app).

## Usage

Vendure Create requires [Node.js](https://nodejs.org/en/) v8.9.0+ to be installed.

To create a new project, you may choose one of the following methods:

### npx

```sh
npx @vendure/create my-app
```

*[npx](https://medium.com/@maybekatz/introducing-npx-an-npm-package-runner-55f7d4bd282b) comes with npm 5.2+ and higher.*

### npm

```sh
npm init @vendure my-app
```

*`npm init <initializer>` is available in npm 6+*

### Yarn

```sh
yarn create @vendure my-app
```

*`yarn create` is available in Yarn 0.25+*


It will create a directory called `my-app` inside the current folder.

## Options

### `--use-npm`

By default, Vendure Create will detect whether a compatible version of Yarn is installed, and if so will display a prompt to select the preferred package manager.
You can override this and force it to use npm with the `--use-npm` flag.

### `--log-level`

You can control how much output is generated during the installation and setup with this flag. Valid options are `silent`, `info` and `verbose`. The default is `silent`

Example:

```sh 
npx @vendure/create my-app --log-level verbose
```
npm package: @shoplyjs/elasticsearch-plugin
Description: The `ElasticsearchPlugin` uses Elasticsearch to power the Vendure product search.
Latest version: 2.3.4

# Vendure Elasticsearch Plugin

The `ElasticsearchPlugin` uses Elasticsearch to power the Vendure product search. 

**Requires Elasticsearch v7.0 or higher.** 

`npm install @vendure/elasticsearch-plugin`

For documentation, see [docs.vendure.io/reference/core-plugins/elasticsearch-plugin/](https://docs.vendure.io/reference/core-plugins/elasticsearch-plugin/)
npm package: @shoplyjs/email-plugin
Description: The `EmailPlugin` generates and sends emails based on Vendure server events.
Latest version: 2.3.6

# Vendure EmailPlugin

The `EmailPlugin` generates and sends emails based on Vendure server events.

`npm install @vendure/email-plugin`

For documentation, see [docs.vendure.io/reference/core-plugins/email-plugin/](https://docs.vendure.io/reference/core-plugins/email-plugin/)
npm package: @shoplyjs/harden-plugin
Description: Hardens your Vendure GraphQL APIs against attacks.
Latest version: 2.3.4

# Vendure Harden Plugin

Hardens your Vendure GraphQL APIs against attacks.

`npm install @vendure/harden-plugin`

For documentation, see [docs.vendure.io/reference/core-plugins/harden-plugin/](https://docs.vendure.io/reference/core-plugins/harden-plugin/)
npm package: @shoplyjs/job-queue-plugin
Description: This plugin includes alternate JobQueueStrategy implementations built on different technologies.
Latest version: 2.3.4

# Vendure Job Queue Plugin

This plugin includes alternate JobQueueStrategy implementations built on different technologies.

Implemented: 

* The `PubSubPlugin` uses Google Cloud Pub/Sub to power the Vendure job queue. 
* The `BullMQJobQueuePlugin` uses Redis via BullMQ.
npm package: @shoplyjs/metrics-plugin
Description: `npm install @vendure/admin-ui-plugin`
Latest version: 2.3.5

# Vendure AdminUiPlugin

`npm install @vendure/admin-ui-plugin`

For documentation, see [docs.vendure.io/reference/core-plugins/admin-ui-plugin/](https://docs.vendure.io/reference/core-plugins/admin-ui-plugin/)
npm package: @shoplyjs/payments-plugin
Description: For documentation, see [docs.vendure.io/reference/core-plugins/payments-plugin/](https://docs.vendure.io/reference/core-plugins/payments-plugin/)
Latest version: 2.3.5

# Payments plugin

For documentation, see [docs.vendure.io/reference/core-plugins/payments-plugin/](https://docs.vendure.io/reference/core-plugins/payments-plugin/)

## Development

### Mollie local development

For testing out changes to the Mollie plugin locally, with a real Mollie account, follow the steps below. These steps
will create an order, set Mollie as payment method, and create a payment intent link to the Mollie platform.

1. Get a test api key from your Mollie
   dashboard: https://help.mollie.com/hc/en-us/articles/115000328205-Where-can-I-find-the-API-key-
2. Create the file `packages/payments-plugin/.env` with content `MOLLIE_APIKEY=your-test-apikey`
3. `cd packages/payments-plugin`
5. `npm run dev-server:mollie`
6. Watch the logs for `Mollie payment link` and click the link to finalize the test payment.

You can change the order flow, payment methods and more in the file `e2e/mollie-dev-server`, and restart the devserver.

### Stripe local development

For testing out changes to the Stripe plugin locally, with a real Stripe account, follow the steps below. These steps
will create an order, set Stripe as payment method, and create a payment secret.

1. Get a test api key from your Stripe
   dashboard: https://dashboard.stripe.com/test/apikeys
2. Use Ngrok or Localtunnel to make your localhost publicly available and create a webhook as described here: https://www.vendure.io/docs/typescript-api/payments-plugin/stripe-plugin/
3. Create the file `packages/payments-plugin/.env` with these contents:
```sh
STRIPE_APIKEY=sk_test_xxxx
STRIPE_WEBHOOK_SECRET=webhook-secret
STRIPE_PUBLISHABLE_KEY=pk_test_xxxx
```
1. `cd packages/payments-plugin`
2. `yarn dev-server:stripe`
3. Watch the logs for the link or go to `http://localhost:3050/checkout` to test the checkout.

After checkout completion you can see your payment in https://dashboard.stripe.com/test/payments/
npm package: @shoplyjs/sentry-plugin
Description: Integrates your Vendure server with the [Sentry](https://sentry.io/) application monitoring service.
Latest version: 2.3.4

# Vendure Sentry Plugin

Integrates your Vendure server with the [Sentry](https://sentry.io/) application monitoring service.

`npm install @vendure/sentry-plugin`

For documentation, see [docs.vendure.io/reference/core-plugins/sentry-plugin/](https://docs.vendure.io/reference/core-plugins/sentry-plugin/)
npm package: @shoplyjs/stellate-plugin
Description: Integrates your Vendure server with the [Stellate](TaxRateEvent) GraphQL API cache.
Latest version: 2.3.4

# Vendure Stellate Plugin

Integrates your Vendure server with the [Stellate](TaxRateEvent) GraphQL API cache.

`npm install @vendure/stellate-plugin`

For documentation, see [docs.vendure.io/reference/core-plugins/stellate-plugin/](https://docs.vendure.io/reference/core-plugins/stellate-plugin/)
npm package: @shoplyjs/testing
Description: End-to-end testing tools for Vendure projects
Author: Michael Bromley
Latest version: 2.3.4

# @vendure/testing

This package contains utilities for writing end-to-end tests for Vendure.

For documentation, see [www.vendure.io/docs/developer-guide/testing/](https://www.vendure.io/docs/developer-guide/testing/)
npm package: @shoplyjs/webhook-plugin
Description: Core webhooks for ShoplyJS
Author: ArseniyX
Latest version: 1.1.1

# Webhooks Plugin

A lightweight plugin that enables subscribing to system events by adding webhooks. Each registered webhook is triggered automatically when an associated event occurs, ensuring real-time notifications and seamless integration.

<img src="./static/logo.png" alt="Wehbook-plugin logo" width="300"/>
npm package: @shopmacher/digest-auth-request
Description: Make digest-auth requests with vanilla javascript
Author: @inorganik
Latest version: 0.8.1

Digest Auth Request
===================

Make digest-auth ajax requests with javascript. Only depency is [CryptoJS MD5](https://code.google.com/p/crypto-js/#MD5).

More info on Digest Auth: http://en.wikipedia.org/wiki/Digest_access_authentication
Currently only supports "auth" quality-of-protection type.

### Usage:

GET request:

```js
var url = 'http://example.com/protected-resource';
		
// create digest request object
var getRequest = new digestAuthRequest('GET', url, 'username', 'password');
		
// make the request
getRequest.request(function(data) { 
  // success callback
  // do something with the data
},function(errorCode) { 
  // error callback
  // tell user request failed
});

// make additional GET requests here...
```
POST request:

```js

var postData = {
   address: '123 main st.',
   city: 'Denver',
   state: 'Colorado'
}

// create new digest request object
// because method (POST vs GET) is different
// otherwise we could re-use the first one
var postReq = new digestAuthRequest('POST', url, 'username', 'password');

postReq.request(function(data) { 
  // success callback
  // data probably a success message
},function(errorCode) { 
  // error callback
  // tell user request failed
}, postData);
```
### Toggle console logging

Out of the box digestAuthRequest.js has logging turned on so you can debug. Set `loggingOn` to false to disable it.

### Contributing

1. Make edits to `digestAuthRequest.js` in the root 
1. In terminal, run `yarn build` or simply `gulp`.
npm package: @shopmacher/ministore
Description: An async dispatch store
Author: Dennis Stockhofe
Latest version: 1.1.2

# ministore [![Build Status](https://travis-ci.org/SHOPMACHER/ministore.svg?branch=master)](https://travis-ci.org/SHOPMACHER/ministore) 

ministore is an async dispatch store.

## Table of Contents

* [Installation](#installation)
  * [UMD](#umd)
  * [AMD](#amd)
  * [CommonJS](#commonjs)
  * [ESM](#esm)
* [Usage](#usage)
  * [Initialization](#initilization)
  * [Register](#register)
  * [Dispatch](#dispatch)
* [Contributing](#contributing)
* [License](#license)

## Installation
Run `npm install -S @shopmacher/ministore` to install the package from npm.
Alternatively, you can download the latest release from this repository.

To include the library, refer to the module definition you are using.

### UMD
Include the `ministore.js` from the `lib` directory
in your project. This makes `ministore` available in the global scope.

### AMD
Adjust your `require.config.js` to include the following code:
```javascript
packages: [{
    name: '@shopmacher/ministore',
    location: 'node_modules/@shopmacher/ministore/lib',
    main: 'ministore'
}]
```

Now you can use the store in your project like this:
```javascript
define('myModule', ['@shopmacher/ministore'], function(Ministore) {
    // Access ministore object here
});
```

### CommonJS
Require the store via `const store = require('@shopmacher/ministore');` and use
the `store` variable to access its methods.

### ESM
Import the store via `import createStore from '@shopmacher/ministore';` and access it
via `const store = createStore();`.

## Usage
This section describes how to initialise the ministore.

### Initialization

Initialize the store with the `createStore()` method:

```javascript
const store = createStore();
```

### Register

You can access the store methods in `store`. Please note, that the handler must return a Promise.

```javascript
store.register('test', {
    handler: asyncFunction()
});
```
Optionally, you can add a priority to the listener object like
```javascript
store.register('test', {
    handler: asyncFunction1(),
    priority: 1
});

store.register('test', {
    handler: asyncFunction2(),
    priority: 2
});
```

### Dispatch
After registering the actions, you can dispatch the action with
```javascript
store.dispatch({ type: 'test' });
```
Also you can add a payload to the dispatch object like
```javascript
store.dispatch({ 
  type: 'test',
  payload: {}
});
```

## Contributing
To contribute to this project, fork the repository and create
your feature/hotfix branch with whatever you want to add.

Install the project dependencies using `npm i` and start the
development server via `npm start`. A webpack-dev-server will now
listen on port 8080.

When you are finished developing, make sure to provide unit tests 
as well as ensure the exsting tests are passing. 
Finally submit a documented pull request.

**Please note:** Pull requests for new features that are not typed via
flowtype as well as not following the general code style used in this
project will be rejected.

## License
MIT
npm package: @shopmeagent/logistics-tracking-mcp
Description: MCP server for international package tracking with multi-carrier support
Author: shopme
Latest version: 1.0.0

# @shopmeagent/logistics-tracking-mcp

MCP server for international package tracking. Supports 3100+ carriers via [17track](https://www.17track.net).

## Quick Start

**Zero-config** (uses Playwright headless browser when no API key is set):

```json
{
  "mcpServers": {
    "logistics-tracking": {
      "command": "npx",
      "args": ["-y", "@shopmeagent/logistics-tracking-mcp"]
    }
  }
}
```

**Recommended** — with 17track API key for best reliability:

```json
{
  "mcpServers": {
    "logistics-tracking": {
      "command": "npx",
      "args": ["-y", "@shopmeagent/logistics-tracking-mcp"],
      "env": {
        "TRACK17_API_KEY": "your-17track-api-key"
      }
    }
  }
}
```

Free API key: https://api.17track.net

## HTTP Server Mode

Deploy with your API key so clients connect via URL without needing their own key:

```bash
export TRACK17_API_KEY=your-key
npx -y @shopmeagent/logistics-tracking-mcp serve
# Listening at http://0.0.0.0:3000/mcp
```

Client config:

```json
{
  "mcpServers": {
    "logistics-tracking": {
      "type": "streamable-http",
      "url": "https://your-domain.com/mcp"
    }
  }
}
```

## Tools

| Tool | Description |
|------|-------------|
| `track_package` | Track a single package by tracking number |
| `detect_carrier` | Identify carrier from tracking number format |
| `batch_track` | Track up to 40 packages at once |
| `explain_status` | Explain tracking status codes |

## Supported Carriers

China Post, China EMS, SF Express, Yanwen, Cainiao, YTO, STO, ZTO, Yunda, Best Express, DHL, FedEx, UPS, USPS, Royal Mail, Japan Post, Korea Post, Australia Post, Singapore Post, Hong Kong Post, Aramex, DPD, and 3000+ more via 17track.

## License

MIT