open-index/open-npm huggingface dataset:
npm package: @nk11/ts-json-yaml
Description: A CLI that allows you to specify your yaml and json files strong-typed using typescript
Author: 7frank
Latest version: 2.0.0

# overview

Goal:

- Define your json files in typescript instead.
- Have full type inference support & some tooling to build json files when you need them
- support json, yaml output

# scripts

- run `npm run dev` to generate typescript interfaces for schemas listed at ts.config.json
    - you will find the schemas at `.schema` delete the folder or a single file to trigger rebuild
 
- configure `npm run dev -- -h`

- run `tsx ./test/example.ts > ./test/example.json` to create json from ts on the fly (Note: this will be done automatically via the configuration)
- or `tsx ./test/traefik.yaml.ts  > ./test/traefik.yaml`


# Example - Azure DevOps Pipelines

Get  a personal access token from your user and for your orga

make sure it has proper permissions otherwise you will get a 401 T_T

`curl  -u :$ADO_PAT "https://dev.azure.com/$ORGA/_apis/distributedtask/yamlschema" >  schema/azure-pipelines.schema.json`

**OR**

`curl  -u :$ADO_PAT "https://dev.azure.com/$ORGA/_apis/distributedtask/yamlschema?api-version=5.1" >  schema/azure-pipelines.schema.json`


# TODO
- "Convert" is not working, 
- bundle size with compile is huge `> 100MB`
npm package: @nk8916/nestjs-package-demo
Description: NestJS npm package starter
Author: Nitin Kumar
Latest version: 1.0.0

<h1 align="center"></h1>

<div align="center">
  <a href="http://nestjs.com/" target="_blank">
    <img src="https://nestjs.com/img/logo_text.svg" width="150" alt="Nest Logo" />
  </a>
</div>

<h3 align="center">NestJS npm Package Starter</h3>

<div align="center">
  <a href="https://nestjs.com" target="_blank">
    <img src="https://img.shields.io/badge/built%20with-NestJs-red.svg" alt="Built with NestJS">
  </a>
</div>

### Installation

1. Clone the repo
2. Run npm/yarn install

```bash
cd nestjs-package-starter
npm install
```

## Change Log

See [Changelog](CHANGELOG.md) for more information.

## Contributing

Contributions welcome! See [Contributing](CONTRIBUTING.md).

## Author

**John Biundo (Y Prospect on [Discord](https://discord.gg/G7Qnnhy))**

## License

Licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
npm package: @nkahr/kontent-migration-cli
Description: Kentico Kontent migration tool
Author: Nina Kahr
Latest version: 0.1.0

# Kentico Migration CLI

This package is a migration runner for [Kentico Kontent](https://kontent.ai/) CMS. It allows the following instructions:

- Tracking migrations in the project
- Creating new content types
- Migrating content types and content changes across types
- Rolling back any changinges

### Gettings started

`yarn`

### Migration spaces

For each Kentico space you should create a different migrations folder. You can set which migrations folder you will be using with the `MIGRATION_FOLDER` environment variable.

### Commands

| Command               | Action                             |
| --------------------- | ---------------------------------- |
| yarn migrate init     | Initiate the migrations in Kontent |
| yarn migrate make     | Make new Kontent migrations        |
| yarn migrate run      | Run new migrations                 |
| yarn migrate rollback | Roll back existing migrations      |

### Environment Variables

To run this project you will need a number of environment variables

| Variable         | Description                       |
| ---------------- | --------------------------------- |
| API_KEY          | Kontent management API key        |
| PROJECT_ID       | Kontent project ID                |
| ENVIRONMENT      | Kontent environment               |
| MIGRATION_FOLDER | The name of the migrations folder |
| PREVIEW_KEY      | Kontent preview API key           |

### Implementation

This project uses [Kontent Migrate](https://github.com/digital-detox/kontent-migration-cli) all the commands used are abstractions from this library.

## Use Cases

### Making a new migration

**Convention for migration description**

- Should start with a capital letter
- Should start with an imperative mood verb

Examples:

- "Create Micro Copy content-type"
- "Add title field to Page content-type"
- "Remove description from all content-types"
npm package: @nkallen/electron-forge-core
Description: A complete tool for building modern Electron applications
Author: Samuel Attard
Latest version: 6.0.5

# Electron Forge Core

This module contains the core logic of Electron Forge and exposes the base
API as a number of simple JS functions.

## Basic Usage

```js
import { api } from '@electron-forge/core';

// Package the current directory as an Electron app
api.package(__dirname);
```

The named export `api` has it's methods documented over at [ForgeAPI](https://js.electronforge.io/api/core/classes/forgeapi).
All the methods are async and expose the core forge methods, please note that all
user-side configuration is still done through your forge config file or the "config.forge"
section of your package.json. This API simply let's you call the methods in
node land without using the CLI.

## Error Handling

As all methods return a promise you should handle all rejections, you should note
that rejections will **not** always be errors, in fact we commonly reject our
promises with just strings so do not assume that properties such as `stack` or
`message` will exist on thrown errors.
npm package: @nkallen/electron-forge-plugin-webpack
Description: Webpack plugin for Electron Forge, lets you use Webpack directly in your tooling
Author: Samuel Attard
Latest version: 6.0.5

## plugin-webpack

This plugin makes it easy to set up standard webpack tooling to compile both your main process code and your renderer process code, with built-in support for Hot Module Replacement (HMR) in the renderer process and support for multiple renderers.

```
// forge.config.js

module.exports = {
  plugins: [
    {
      name: '@electron-forge/plugin-webpack',
      config: {
        mainConfig: './webpack.main.config.js',
        renderer: {
          config: './webpack.renderer.config.js',
          entryPoints: [{
            name: 'main_window',
            html: './src/renderer/index.html',
            js: './src/renderer/index.js',
            preload: {
              js: './src/preload.js'
            }
          }],
        }
      }
    }
  ]
}
```