open-index/open-npm huggingface dataset:
npm package: @prodigyai/restify-cors-middleware
Description: Common middlewares for all Node.js web services
Author: Tabcorp Digital Technology Team
Latest version: 2.0.0

# restify-cors-middleware

> CORS middleware with full [W3C spec](www.w3.org/TR/cors) support.

[![NPM](http://img.shields.io/npm/v/restify-cors-middleware.svg?style=flat)](https://npmjs.org/package/restify-cors-middleware)
[![License](http://img.shields.io/npm/l/restify-cors-middleware.svg?style=flat)](https://github.com/TabDigital/restify-cors-middleware)

[![Build Status](http://img.shields.io/travis/TabDigital/restify-cors-middleware.svg?style=flat)](http://travis-ci.org/TabDigital/restify-cors-middleware)
[![Dependencies](http://img.shields.io/david/TabDigital/restify-cors-middleware.svg?style=flat)](https://david-dm.org/TabDigital/restify-cors-middleware)
[![Dev dependencies](http://img.shields.io/david/dev/TabDigital/restify-cors-middleware.svg?style=flat)](https://david-dm.org/TabDigital/restify-cors-middleware)
[![Peer dependencies](http://img.shields.io/david/peer/TabDigital/restify-cors-middleware.svg?style=flat)](https://david-dm.org/TabDigital/restify-cors-middleware)
[![Known Vulnerabilities](https://snyk.io/package/npm/restify-cors-middleware/badge.svg)](https://snyk.io/package/npm/restify-cors-middleware)

[![JavaScript Style Guide](https://cdn.rawgit.com/feross/standard/master/badge.svg)](https://github.com/feross/standard)

## Usage

```js
const corsMiddleware = require('restify-cors-middleware')

const cors = corsMiddleware({
  preflightMaxAge: 5, //Optional
  origins: ['http://api.myapp.com', 'http://web.myapp.com'],
  allowHeaders: ['API-Token'],
  exposeHeaders: ['API-Token-Expiry']
})

server.pre(cors.preflight)
server.use(cors.actual)
```

## Allowed origins

You can specify the full list of domains and subdomains allowed in your application:

```js
origins: [
  'http://myapp.com',
  'http://*.myapp.com'
]
```

For added security, this middleware sets `Access-Control-Allow-Origin` to the origin that matched, not the configured wildcard.
This means callers won't know about other domains that are supported.

Setting `origins: ['*']` is also valid, although it comes with obvious security implications. Note that it will still return a customised response (matching Origin), so any caching layer (reverse proxy or CDN) will grow in size accordingly.

## Troubleshooting

As per the spec, requests without an `Origin` will not receive any headers. Requests with a matching `Origin` will receive the appropriate response headers. Always be careful that any reverse proxies (e.g. Varnish) very their cache depending on the origin, so you don't serve CORS headers to the wrong request.

## Compliance to the spec

See [unit tests](https://github.com/TabDigital/restify-cors-middleware/tree/master/test) for examples of preflight and actual requests.
npm package: @prodigytech/js-dependency-check
Description: A utility that checks a projects dependencies and returns a report of the which dependencies are out of date, deprecated, or up to date
Latest version: 6.0.1

## Project Dependency Checker

The Project Dependency Checker is a powerful utility tool that serves as a Dev Dependency add-on for your JavaScript projects. Its primary function is to provide you with a comprehensive and insightful report on your project's dependencies, giving you a clear indication of their update status. By comparing your project dependencies against the npm registry, this tool ensures that you are aware of any outdated dependencies that may impact your project's stability and security.

### Installation

To integrate this package into your project, simply execute one of the following commands:

```bash
yarn add @prodigytech/js-dependency-check -D
```

or

```bash
npm install @prodigytech/js-dependency-check --save-dev
```

### Setup

Setting up the utility is a breeze, and you have multiple options to choose from:

1. **package.json Configuration:** You can conveniently configure the utility by adding a `dependencyCheckConfig` object to your project's `package.json` file. This configuration allows you to customize the report type, specify the fail-on criteria, and even define specific packages to ignore.

```json
"dependencyCheckConfig": {
    "reportType": "CI|HTML|JSON",
    "failOn": "MAJOR|MINOR|NONE",
    "ignorePackages": [
        "@babel/preset-env",
        "..."
    ]
}
```

2. **Standalone JSON Configuration:** Alternatively, you can create a separate JSON configuration file named `dependencyCheckConfig.json`. This file provides a clean and dedicated space to configure the utility with the desired report type, fail-on criteria, and any packages you wish to exclude.

```json
{
    "reportType": "CI|HTML|JSON",
    "failOn": "MAJOR|MINOR|NONE",
    "ignorePackages": [
        "@babel/preset-env",
        "..."
    ]
}
```

3. **Command-Line Arguments:** For those who prefer flexibility and quick setup, the utility also supports configuration through command-line arguments. Simply pass the desired options when running the utility command.

```bash
npx @prodigytech/js-dependency-check --reportType "CI|HTML|JSON" --failOn "MAJOR|MINOR|NONE" --ignorePackages axios react eslint
```

### Usage

Using the Project Dependency Checker is straightforward and user-friendly:

1. Ensure that you have successfully added the utility as a dependency in your project.
2. Configure the utility according to your preferences, utilizing any of the available configuration methods: `package.json`, standalone JSON file, or command-line arguments.
3. Execute the following command to run the utility:

```bash
npx @prodigytech/js-dependency-check
```

The generated report will be saved to the root directory of your project for JSON and HTML report types. If you choose the `CI` report type, it will be directly displayed on your screen. Additionally, if you have configured the fail-on option with packages that meet the specified criteria, the process will gracefully exit with a non-zero exit code.
npm package: @prodio-app/journey
Description: Prodio - Journey for building advanced user onboarding tours. Supports no-code or in-code flows. With advanced features like Wait or Conditional steps to create the ultimate onboarding tour, boosting product adoption. Optimize user journey, increase engag
Latest version: 1.0.0

<p align="center">
  <img alt="Prodio banner" src="./docs/github-banner.png">
</p>
<h1 align="center">Prodio SDKs</h1>

## Getting started

Build native product growth experiences, your way – Meet Prodio, the flexible platform for building in-app experiences. Focus on your product, not creating one-off logic.

- Build powerful in-app experiences to drive product growth
- Embed components directly into your app
- Create onboarding, product adoption, in-app messaging, growth experiments, and more
- Bring your own UI components or use Prodio built-in components

Visit our [website](https://prodio.app) to learn more about Prodio

## Documentation

Visit [https://docs.prodio.app](https://docs.prodio.app) for full documentation.