open-index/open-npm huggingface dataset:
npm package: @pablosz/bob-the-bundler
Description: Bob The Bundler!
Author: Kamil Kisiela
Latest version: 1.5.2

# Bob (The Bundler)

There's no documentation yet but you can check [GraphQL Code Generator](https://github.com/dotansimha/graphql-code-generator) repository to see how to use Bob.

## Requirements

- Supports only scoped packages (same scope)
- Yarn Workspaces
- TypeScript with Paths
- It's so strict you shouldn't use it!

## Configuration

Bob only accepts `bob.config.js` in root directory:

```js
module.exports = {
  scope: "@graphql-codegen", // Scope of organization
  ignore: ["@graphql-codegen/website", "@graphql-codegen/live-demo"], // ignored packages
  track: [
    // files in root that mark the entire workspace as dirty
    "bob.config.js", // we could include it in Bob itself but we decided to turn your life into hell :)
    "jest.config.js",
    "jest-project.js",
    "package.json",
    "tsconfig.json",
    // files in packages that mark the package as dirty
    "<project>/src/**",
    "<project>/jest.config.js",
    "<project>/package.json",
    "<project>/tsconfig.json",
  ],
  base: "origin/master", // we need to compare against something
  commands: {
    test: {
      track: ["<project>/tests/**"],
      run(affected) {
        // {
        //   paths: string[] <- ['packages/core', 'packages/cli']
        //   names: string[] <- ['@foo/core', '@foo/cli']
        // }

        // why such a weird syntax? We use spawn, so you have too
        return [`yarn`, ["test", ...affected.paths]];
      },
    },
    build: {
      run() {
        return [`yarn`, ["build"]];
      },
    },
  },
};
```

## Build Options

In your `<project>/package.json`:

```json
{
  "buildOptions": {
    "external": ["simple-git/promise"], // Marks nested imports as external
    "bin": {
      "cli": {
        "input": "src/cli.ts" // Entry point for `cli` command
      }
    }
  }
}
```

## Support for Node ES Modules

In your `<project>/package.json`, just add `"exports"` like this:

```json
{
  "main": "dist/index.cjs.js",
  "exports": {
    "require": "dist/index.cjs.js", // should match "main"
    "default": "dist/index.mjs" // should ends with ".mjs" extension
  }
}
```

## Usage

```bash

$ bob affected test
$ bob affected build

$ bob build
$ bob prepack

$ bob runify

```
npm package: @pablosz/esbuild-node-tsc
Description: Build your Typescript Node.js projects using blazing fast esbuild
Latest version: 1.0.2

# ⚡️ esbuild-node-tsc

Build your Typescript Node.js projects using blazing fast **[esbuild](https://github.com/evanw/esbuild)**.

Since esbuild can build large typescript node projects in subsecond speeds, this is quite useful for development builds too if you want to stick with `tsc` for production builds.

**_Please note this library doesnt do typechecking. For typechecking please continue to use tsc._**

## How does it work?

esbuild-node-tsc reads the tsconfig.json and builds the typescript project using esbuild. esbuild is the fastest typescript builder around. It also copies the non ts files such as json, graphql files, images,etc to the dist folder. If the assets are not copied correctly check the configuration guide below.

## Installation

```
npm install --save-dev esbuild-node-tsc
```

## Usage

```
npx esbuild-node-tsc
```

or use the short form.

```
npx etsc
```

Additionally, you can add it to your build scripts

```json
{
  "name": "myproject",
  "version": "0.1.0",
  "scripts": {
    "dev": "etsc" 
  }
}
```

Then just run

```
npm run dev
```

## Live reloading (nodemon ❤️ esbuild-node-tsc)

Since esbuild can build large typescript projects in subsecond speeds you can use this library instead of ts-node-dev or ts-node which usually slow down when project scales.

To achieve live reloading:

```
npm install --save-dev nodemon esbuild-node-tsc
```

Then add the following script to package.json

```json
{
  "name": "myproject",
  "version": "0.1.0",
  "scripts": {
    "dev": "nodemon"
  }
}
```

And add a `nodemon.json`

```json
{
  "watch": ["src"],
  "ignore": ["src/**/*.test.ts"],
  "ext": "ts,mjs,js,json,graphql",
  "exec": "etsc && node ./dist/index.js",
  "legacyWatch": true
}
```

Finally run

```
npm run dev
```

## Comparison with tsc

<img src="https://user-images.githubusercontent.com/4029423/94347242-c6497600-0032-11eb-8a66-4311adf04554.gif" width="638" height="750">


## Optional configuration

By default esbuild-node-tsc should work out of the box for your project since it reads the necessary configuration from your tsconfig.json

But if things are not working as expected you can configure esbuild-node-tsc by adding `etsc.config.js` along side tsconfig.json.

Example `etsc.config.js`

```js
module.exports = {
  outDir: "./dist",
  esbuild: {
    minify: false,
    target: "es2015",
  },
  assets: {
    baseDir: "src",
    filePatterns: ["**/*.json"],
  },
};
```

All of the above fields are optional

## License

MIT
npm package: @pablosz/fastify-nextjs
Description: React server side rendering support for Fastify with Next
Author: Tomas Della Vedova - @delvedor
Latest version: 5.0.4

# fastify-nextjs

[![js-standard-style](https://img.shields.io/badge/code%20style-standard-brightgreen.svg?style=flat)](http://standardjs.com/)  ![CI workflow](https://github.com/fastify/fastify-nextjs/workflows/CI%20workflow/badge.svg)

React server side rendering support for Fastify with [Next](https://github.com/zeit/next.js/#custom-server-and-routing) Framework.

## Install
```
npm i fastify-nextjs next --save
```

## Usage
Since Next needs some time to be ready on the first launch, you must declare your routes inside the `after` callback, after you registered the plugin.  
The plugin will expose the api `next` in Fastify that will handle the rendering for you.  
```js
const fastify = require('fastify')()

fastify
  .register(require('fastify-nextjs'))
  .after(() => {
    fastify.next('/hello')
  })

fastify.listen(3000, err => {
  if (err) throw err
  console.log('Server listening on http://localhost:3000')
})
```

All you server rendered pages must be saved in the folder `pages`, as you can see in the [next documentation](https://github.com/zeit/next.js/#custom-server-and-routing).
```js
// /pages/hello.js
export default () => <div>hello world</div>
```
If you need to pass [custom options](https://github.com/zeit/next.js/#custom-configuration) to `next` just pass them to register as second parameter.
```js
fastify.register(require('fastify-nextjs'), { dev: true })
```

If you need to handle the render part yourself, just pass a callback to `next`:
```js
fastify.next('/hello', (app, req, reply) => {
  // your code
  // `app` is the Next instance
  app.render(req.raw, reply.raw, '/hello', req.query, {})
})
```
## Acknowledgements

This project is kindly sponsored by:
- [nearForm](http://nearform.com)
- [LetzDoIt](http://www.letzdoitapp.com/)

## License

Licensed under [MIT](./LICENSE).
npm package: @pablosz/gqless
Description: gqless client without queries
Author: GQless
Latest version: 2.0.15

# [GQless](https://gqless.com/getting-started) [![Documentation](https://img.shields.io/badge/documentation-documentation?color=C00B84)](https://gqless.com) [![Twitter](https://img.shields.io/twitter/follow/gqlessdev?label=%40gqlessdev&style=flat&logo=twitter&color=00acee)](https://twitter.com/gqlessdev)

> GQless is a fully-featured GraphQL client, which lowers the barrier of entry towards using GraphQL.

Data requirements within your application are picked up automatically, freeing you from having to maintain GraphQL queries by-hand. It offers a first-class TypeScript experience. See API documentation at all times within autocomplete.

Make breaking changes to your API, and see type-errors exactly where things are breaking, in realtime. No more running a separate validation step.

**More documentation is available at [gqless.com/getting-started](https://gqless.com/getting-started).**

<a href="https://gqless.com">
  <img alt="Example usage" src="https://user-images.githubusercontent.com/13242392/112103674-fddc4980-8ba1-11eb-8c83-b527dcb0243d.PNG" />
</a>
npm package: @pablosz/gqless-cli
Description: ## Visit [https://gqless.com/cli/codegen](https://gqless.com/cli/codegen)
Author: GQless
Latest version: 2.0.18

# @pablosz/gqless-cli

## Visit [https://gqless.com/cli/codegen](https://gqless.com/cli/codegen)
npm package: @pablosz/gqless-react
Description: ## Visit [https://gqless.com/react/fetching-data](https://gqless.com/react/fetching-data)
Author: GQless
Latest version: 2.0.16

# @pablosz/gqless-react

## Visit [https://gqless.com/react/fetching-data](https://gqless.com/react/fetching-data)
npm package: @pablosz/gqless-schema
Description: Creates a `gqless` schema from a GraphQL endpoint.
Latest version: 0.0.6

# @gqless/schema

Creates a `gqless` schema from a GraphQL endpoint.

- [**Codegen (typesafe)**](#Codegen) - outputs an array containing JS sourcecode, used by the CLI
- [**Runtime (not-typesafe)**](#Runtime) - creates a schema in the browser/node without codegen

## Usage

### Codegen

```js
import { Codegen, fetchSchema } from '@gqless/schema'

const schemaDefs = await fetchSchema(fetchQuery)
const codegen = new Codegen(schemaDefs, { typescript: true })

const files = codegen.generate()
// => { path: string, contents: string }[]
```
npm package: @pablosz/nexus-prisma
Author: Jason Kuhrt
Latest version: 2.0.2

**⚠️ Currently in early preview - _not to be used in Production unless you're willing to live on the bleeding edge and give us feedback, which we would welcome!_** Follow progress [here](https://github.com/graphql-nexus/nexus-plugin-prisma/issues/1039).

<p align="center">
  <img src="https://i.imgur.com/8qvElTM.png" width="300" align="center" />
  <h1 align="center"><a style="color:black;" href="https://nexus.prisma.io">nexus-prisma</a></h1>
</p>

[![trunk](https://github.com/prisma/nexus-prisma/actions/workflows/trunk.yml/badge.svg)](https://github.com/prisma/nexus-prisma/actions/workflows/trunk.yml)

Official [Prisma](https://prisma.io) plugin for [Nexus](https://nexusjs.org).

Please visit [nexus.prisma.io](https://nexus.prisma.io) for documentation.
npm package: @pablosz/open-terminal
Description: cross platform open terminal and run command
Author: Clay Risser
Latest version: 0.1.12

# open-terminal

[![GitHub stars](https://img.shields.io/github/stars/clayrisser/open-terminal.svg?style=social&label=Stars)](https://github.com/clayrisser/open-terminal)

> cross platform open terminal and run command

Please ★ this repo if you found it useful ★ ★ ★

## Features

- supports osx
- supports linux

## Installation

```sh
npm install -g open-terminal
```

## Dependencies

- [NodeJS](https://nodejs.org)

## Usage

### from the terminal

```sh
open-terminal "echo 'Hello, world!' && tail -f /dev/null"
```

### from the nodejs api

```js
import openTerminal from 'open-terminal';

openTerminal("echo 'Hello, world!' && tail -f /dev/null");
```

## Support

Submit an [issue](https://github.com/clayrisser/open-terminal/issues/new)

## Screenshots

[Contribute](https://github.com/clayrisser/open-terminal/blob/master/CONTRIBUTING.md) a screenshot

## Contributing

Review the [guidelines for contributing](https://github.com/clayrisser/open-terminal/blob/master/CONTRIBUTING.md)

## License

[MIT License](https://github.com/clayrisser/open-terminal/blob/master/LICENSE)

[Clay Risser](https://clayrisser.com) © 2021

## Changelog

Review the [changelog](https://github.com/clayrisser/open-terminal/blob/master/CHANGELOG.md)

## Credits

- [Clay Risser](https://clayrisser.com) - Author

## Support on Liberapay

A ridiculous amount of coffee ☕ ☕ ☕ was consumed in the process of building this project.

[Add some fuel](https://liberapay.com/clayrisser/donate) if you'd like to keep me going!

[![Liberapay receiving](https://img.shields.io/liberapay/receives/clayrisser.svg?style=flat-square)](https://liberapay.com/clayrisser/donate)
[![Liberapay patrons](https://img.shields.io/liberapay/patrons/clayrisser.svg?style=flat-square)](https://liberapay.com/clayrisser/donate)
npm package: @pablosz/react-image-pan-zoom-rotate
Description: Simple wrapper for pan, zoom, rotate on react containers
Author: mgorabbani
Latest version: 1.3.1

![npm type definitions](https://img.shields.io/npm/types/typescript.svg?label=lang)
# React Pan, Zoom & Rotate

A simple pan and zoom and rotating for images in react.

## Demo
![](https://media.giphy.com/media/WVGLHnLLSREM6lqmWe/source.gif)

[![Edit q8wl1joow9](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/n1rv671pkj)

## Installation

```
> yarn add react-image-pan-zoom-rotate
```

## Features
- Drag & Move
- Zoom In 
- Zoom Out
- Rotate (in Left only) 


## Usage

```typescript
import ReactPanZoom from 'react-image-pan-zoom-rotate';
class MyComponent extends React.PureComponent {
  public render() {
    return (
      <ReactPanZoom image="https://drscdn.500px.org/photo/105738331/q%3D80_m%3D2000/v2?webp=true&sig=538a4f76f4966c84acb01426bb4a4a5e4a85b72a2c3bd64973d3a369f9653007" alt="document image"/>
    );
  }
}
```
npm package: @pablosz/tsup
Description: [![npm version](https://badgen.net/npm/v/tsup)](https://npm.im/tsup) [![npm downloads](https://badgen.net/npm/dm/tsup)](https://npm.im/tsup)
Author: EGOIST
Latest version: 0.2.1

# tsup

[![npm version](https://badgen.net/npm/v/tsup)](https://npm.im/tsup) [![npm downloads](https://badgen.net/npm/dm/tsup)](https://npm.im/tsup)

Bundle your TypeScript library with no config, powered by [esbuild](https://github.com/evanw/esbuild).

## Quick Start

```bash
tsup src/index.ts
```

This will bundle `src/index.ts` to `dist/index.js`.

## Documentation

https://tsup.egoist.sh

## License

MIT &copy; [EGOIST](https://github.com/sponsors/egoist)
npm package: @pabloxt14-ignite-ui/react
Description: Este é o pacote de componentes React do **Design System Ignite UI**, desenvolvido por [Pablo Alan](https://www.linkedin.com/in/pabloalan/) como parte do bootcamp Ignite da [Rocketseat](https://www.rocketseat.com.br/).
Latest version: 3.0.1

# @pabloxt14-ignite-ui/react ⚛

Este é o pacote de componentes React do **Design System Ignite UI**, desenvolvido por [Pablo Alan](https://www.linkedin.com/in/pabloalan/) como parte do bootcamp Ignite da [Rocketseat](https://www.rocketseat.com.br/).

Esta pacote contém componentes React reutilizáveis criados para facilitar o desenvolvimento de interfaces consistentes e agradáveis.

Este pacote contém uma ampla variedade de componentes prontos para uso, como avatar, box, button, heading, toast e muito mais. Cada componente é cuidadosamente projetado para ser flexível, personalizável e compatível com as melhores práticas de design.

Para obter exemplos de uso e documentação detalhada sobre os componentes disponíveis neste pacote, recomendamos acessar a documentação Storybook dedicada. Lá você encontrará guias, exemplos de código e demos interativas para facilitar o uso e a personalização dos componentes.

**Documentação Storybook**: https://pabloxt14.github.io/Ignite-Design-System/

Sinta-se à vontade para utilizar esses componentes em seus projetos React para economizar tempo e garantir uma experiência de usuário consistente. Se tiver dúvidas, problemas ou sugestões, fique à vontade para abrir uma issue no repositório do pacote no GitHub.

**GitHub**: https://github.com/PabloXT14/Ignite-Design-System/
npm package: @pabloxt14-ignite-ui/tokens
Description: Este é o pacote de tokens do **Design System Ignite UI**, desenvolvido por [Pablo Alan](https://www.linkedin.com/in/pabloalan/) como parte do bootcamp Ignite da [Rocketseat](https://www.rocketseat.com.br/).
Latest version: 1.1.1

# @pabloxt14-ignite-ui/tokens 🎨

Este é o pacote de tokens do **Design System Ignite UI**, desenvolvido por [Pablo Alan](https://www.linkedin.com/in/pabloalan/) como parte do bootcamp Ignite da [Rocketseat](https://www.rocketseat.com.br/).

Os tokens são elementos essenciais para a consistência visual e a padronização de estilos em um projeto. Este pacote contém uma coleção abrangente de tokens de design, como cores, tipografia, espaçamento e outros elementos visuais.

Para visualizar e explorar os tokens disponíveis neste pacote, recomendamos acessar a documentação Storybook dedicada. Lá você encontrará detalhes sobre cada token, incluindo exemplos visuais e instruções de uso.

**Documentação Storybook**: https://pabloxt14.github.io/Ignite-Design-System/?path=/docs/tokens

Fique à vontade para usar esses tokens em seus projetos para garantir uma experiência visual consistente e um design harmonioso. Se tiver dúvidas, problemas ou sugestões, sinta-se à vontade para abrir uma issue no repositório do pacote no GitHub.

**GitHub**: https://github.com/PabloXT14/Ignite-Design-System/