open-index/open-npm huggingface dataset:
npm package: @francesco.panciroli/tickets-npm-module
Description: Demo ticket service with Fastify and MongoDB
Author: Francesco Panciroli
Latest version: 0.2.0
Deprecated: false

# fastify-mongo-tickets

Demo ticket service with Fastify and MongoDB

## Install

```
npm i @matteo.collina/fastify-mongo-tickets
```

## Usage

```js
'use strict'

const Fastify = require('fastify')

const app = Fastify()

app.register(require('fastify-jwt'), {
  secret: 'averyverylongsecret'
})

app.register(require('fastify-mongodb'), {
  url: 'mongodb://localhost:27017',
  useNewUrlParser: true
})

app.register(require('@matteo.collina/fastify-mongo-tickets'))

app.listen(3000)
```

Works best in combo with
[https://github.com/mcollina/fastify-auth-mongo-jwt](https://github.com/mcollina/fastify-auth-mongo-jwt).

## API

Docs TBD, see tests.
It uses [fastify-mongodb](https://github.com/fastify-mongodb) and [fastify-jwt](https://github.com/fastify-jwt)

## License

MIT
npm package: @francescodevalerio/tmdb-ts
Description: TMDB v3 library wrapper
Author: Blake Joynes
Latest version: 1.8.4

# tmdb-ts


Typescript library wrapper of [TMDB API](https://developers.themoviedb.org/) v3 .

Forked from [tmsb-ts](https://github.com/blakejoy/tmdb-ts)! Thanks!


[![Version npm](https://img.shields.io/npm/v/tmdb-ts.svg?style=flat-square)](https://www.npmjs.com/package/tmdb-ts)[![npm Downloads](https://img.shields.io/npm/dm/tmdb-ts.svg?style=flat-square)](https://npmcharts.com/compare/tmdb-ts?minimal=true)

This uses new jwt authentication token for requests so there is no need to append api key to the url. 
Once you have registered for access to the api you can use your access token as follows:

Installation:
``
npm install --save tmdb-ts
``

Version 1.0 removed the default import so make sure you update accordingly!

```js
import { TMDB } from 'tmdb-ts';

const tmdb = new TMDB('accessToken');

try {
   const movies = await tmdb.search.movies({ query: 'American Pie' });
   console.log(movies);
} catch(err) {
   // handle error
}
```
npm package: @francescog/use-render-tracker
Description: A React hook to track component renders, prop/state changes, and render performance
Author: Francesco/CavalloPepperone
Latest version: 1.0.1

# React + Vite

This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.

Currently, two official plugins are available:

- [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react) uses [Babel](https://babeljs.io/) for Fast Refresh
- [@vitejs/plugin-react-swc](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react-swc) uses [SWC](https://swc.rs/) for Fast Refresh

## Expanding the ESLint configuration

If you are developing a production application, we recommend using TypeScript with type-aware lint rules enabled. Check out the [TS template](https://github.com/vitejs/vite/tree/main/packages/create-vite/template-react-ts) for information on how to integrate TypeScript and [`typescript-eslint`](https://typescript-eslint.io) in your project.
npm package: @francescozoccheddu/pidby
Description: PDF creator from web pages with built-in Pug, EJS, Sass and TypeScript support
Author: Francesco Zoccheddu
Latest version: 0.0.17

# pidby
PDF creator from web pages with built-in [Pug](https://pugjs.org/), [EJS](https://ejs.co/), [Sass](https://sass-lang.com/) and [TypeScript](https://www.typescriptlang.org/) support.

## Installation
Run
```shell
npm i -g @francescozoccheddu/pidby
```

## Usage

Run
```shell
pidby --help
```

You can try it with the included [example](/example):
```shell
git clone https://github.com/francescozoccheddu/pidby
cd pidby
pidby run example/config.yml output.pdf
```
npm package: @francescozoccheddu/reload-please
Description: Lightweight server and client script to trigger a browser page reload
Author: Francesco Zoccheddu
Latest version: 0.0.3

# reload-please

Lightweight server and client script to trigger a browser page reload.

## Installation

Run:

```shell
npm i @francescozoccheddu/reload-please
```

## Usage

### Server

```javascript
import { Server } from "@francescozoccheddu/reload-please";

const server = new Server();
server.start();
// [...]
server.reload();
// [...]
server.stop();
```

### Client

```javascript
import { Client } from "@francescozoccheddu/reload-please";

const client = new Client();
client.start();
// [...]
client.stop();
```

> [!TIP]
> You can also use `server.clientScript` or `getClientScript()` to inject the client code server-side, on the fly.

## Build

Run:

```shell
npm run build
```
npm package: @francis.tec/npmvet
Description: A simple CLI tool for vetting npm package versions
Author: Andrew Hathaway
Latest version: 0.1.6

![](./.github/banner.png?raw=true)

[![Build status](https://ci.appveyor.com/api/projects/status/e6e1rgx0i853jg8b/branch/master?svg=true)](https://ci.appveyor.com/project/andrewhathaway/npmvet/branch/master)


NPM Vet is a simple CLI tool to help vet your npm package versions. NPM Vet can be used locally, or as a CI build-step to prevent builds passing with mismatched package versions. To read more about NPM Vet, visit the [Hark website](https://harksys.com/labs/npm-vet-a-simple-cli-tool-for-checking-npm-package-versions).

## Installation

    $ npm install npmvet -g

## Usage

    Usage: npmvet [options]

    Options:

      -h, --help                 output usage information
      -V, --version              output the version number
      -p, --package <package>    package.json file location (Default: .)
      -m, --modules <modules>    node_modules folder location (Default: .)
      -r, --renderer <renderer>  Renderer to use (Default: inlinetable)
      -s, --strict               Using the CI renderer, fail build if any packages unlocked (Default: false, flag)

## Strict Mode

If you're using the CI renderer (see below) the `-s` flag will enable strict mode. In which builds will fail if versions are unlocked, not just unmatching.

## Renderers

Renderers are used to dictate how to output the data NPM Vet collects. The default is `inlinetable`.

### Inline Table

    $ npmvet -r inlinetable

The default renderer, `inlinetable` will print a table inline with your current process. You can use this locally to visualise package differences.

![](./.github/inlinetable.png?raw=true)

### CI

    $ npmvet -r ci

To prevent your CI builds passing with mismatched package versions, use the CI renderer. If any package version mismatches are found, the build will fail:

![](./.github/ci-error.png?raw=true)

Or if there are no mismatching package versions, your build will continue (and hopefully pass!):

![](./.github/ci-success.png?raw=true)

### Blessed

The `blessed` renderer will render a table inside a screen, that has be exited by the user to escape.

    $ npmvet -r blessed

![](./.github/blessed.png?raw=true)

### JSON
The `JSON` renderer will print a JSON array with match information for each package.

    $ npmvet -r json

```json
[
  {
    "name": "blessed",
    "packageVersion": "0.1.81",
    "installedVersion": "0.1.81",
    "matches": true,
    "locked": false
  },
  {
    "name": "chalk",
    "packageVersion": "1.1.3",
    "installedVersion": "1.1.3",
    "matches": true,
    "locked": false
  },
  {
    "name": "jest",
    "packageVersion": "18.1.0",
    "installedVersion": "18.1.0",
    "matches": true,
    "locked": false
  }
]
```

## Contributing

For information regarding contributing to this project, please read the [Contributing](./CONTRIBUTING.md) document.

## License

[MIT License](./LICENSE.md)