open-index/open-npm huggingface dataset:
npm package: @halkeye/jenkins-io-components
Description: Random parts shared between jenkins.io
Author: Gavin Mogan
Latest version: 1.10.0

# Welcome to Jenkins.io Web Components

This is an attempt to build web components that can be used across various jenkins.io based projects

## Setup

Install dependencies:

```bash
npm i
```

## Build

This sample uses the TypeScript compiler to produce JavaScript that runs in modern browsers.

To build the JavaScript version of your component:

```bash
npm run build
```

To watch files and rebuild when the files are modified, run the following command in a separate shell:

```bash
npm run build:watch
```

Both the TypeScript compiler and lit-analyzer are configured to be very strict. You may want to change `tsconfig.json` to make them less strict.

## Testing

This sample uses modern-web.dev's
[@web/test-runner](https://www.npmjs.com/package/@web/test-runner) for testing. See the
[modern-web.dev testing documentation](https://modern-web.dev/docs/test-runner/overview) for
more information.

Tests can be run with the `test` script, which will run your tests against Lit's development mode (with more verbose errors) as well as against Lit's production mode:

```bash
npm test
```

For local testing during development, the `test:dev:watch` command will run your tests in Lit's development mode (with verbose errors) on every change to your source files:

```bash
npm test:watch
```

Alternatively the `test:prod` and `test:prod:watch` commands will run your tests in Lit's production mode.

## Dev Server

To run the dev server and open the project in a new browser tab:

```bash
npm run storybook
```

## Editing

If you use VS Code, we highly recommend the [lit-plugin extension](https://marketplace.visualstudio.com/items?itemName=runem.lit-plugin), which enables some extremely useful features for lit-html templates:

- Syntax highlighting
- Type-checking
- Code completion
- Hover-over docs
- Jump to definition
- Linting
- Quick Fixes

The project is setup to recommend lit-plugin to VS Code users if they don't already have it installed.

## Linting

Linting of TypeScript files is provided by [ESLint](eslint.org) and [TypeScript ESLint](https://github.com/typescript-eslint/typescript-eslint). In addition, [lit-analyzer](https://www.npmjs.com/package/lit-analyzer) is used to type-check and lint lit-html templates with the same engine and rules as lit-plugin.

The rules are mostly the recommended rules from each project, but some have been turned off to make LitElement usage easier. The recommended rules are pretty strict, so you may want to relax them by editing `.eslintrc.json` and `tsconfig.json`.

To lint the project run:

```bash
npm run lint
```

## Formatting

[Prettier](https://prettier.io/) is used for code formatting. It has been pre-configured according to the Lit's style. You can change this in `.prettierrc.json`.

Prettier has not been configured to run when committing files, but this can be added with Husky and and `pretty-quick`. See the [prettier.io](https://prettier.io/) site for instructions.
npm package: @halkeye/jenkins-io-react
Description: Random parts shared between jenkins.io
Author: Gavin Mogan
Latest version: 0.0.9

# Welcome to @halkeye/jenkins-io-react 👋
[![Version](https://img.shields.io/npm/v/@halkeye/jenkins-io-react.svg)](https://www.npmjs.com/package/@halkeye/jenkins-io-react)
[![Documentation](https://img.shields.io/badge/documentation-yes-brightgreen.svg)](https://github.com/halkeye/jenkins-io-react#readme)
[![Maintenance](https://img.shields.io/badge/Maintained%3F-yes-green.svg)](https://github.com/halkeye/jenkins-io-react/graphs/commit-activity)
[![License: MIT](https://img.shields.io/github/license/halkeye/@halkeye/jenkins-io-react)](https://github.com/halkeye/jenkins-io-react/blob/master/LICENSE)
[![Twitter: halkeye](https://img.shields.io/twitter/follow/halkeye.svg?style=social)](https://twitter.com/halkeye)

> Random parts shared between jenkins.io

## Install

```sh
npm install
```

## Run tests

```sh
npm run test
```

## Author

👤 **Gavin Mogan

* Website: [https://www.gavinmogan.com](https://www.gavinmogan.com)
* Twitter: [@halkeye](https://twitter.com/halkeye)
* Github: [@halkeye](https://github.com/halkeye)
* LinkedIn: [@halkeye](https://linkedin.com/in/halkeye)

## Show your support

Give a ⭐️ if this project helped you!


## 📝 License

Copyright © 2022 [Gavin Mogan](https://github.com/halkeye).

This project is [MIT](https://opensource.org/licenses/MIT) licensed.

***
_This README was generated with ❤️ by [readme-md-generator](https://github.com/kefranabg/readme-md-generator)_
npm package: @halkeye/tscpaths
Description: Replace absolute paths to relative paths after typescript compilation
Author: Jon Wheeler @jonkwheeler
Latest version: 0.0.9

# tscpaths
Replace absolute paths to relative paths after typescript compilation (tsc) during compile-time.

[![npm version](https://badge.fury.io/js/tscpaths.svg)](https://badge.fury.io/js/tscpaths)
[![Dependency Status](https://david-dm.org/joonhocho/tscpaths.svg)](https://david-dm.org/joonhocho/tscpaths)
[![License](http://img.shields.io/:license-mit-blue.svg)](http://doge.mit-license.org)

## Comparison to [tsconfig-paths](https://github.com/dividab/tsconfig-paths)
\+ Compile time (no runtime dependencies)

## Getting Started
First, install tscpaths as devDependency using npm or yarn.

```sh
npm install --save-dev tscpaths
# or
yarn add -D tscpaths
```

## Add it to your build scripts in package.json
```json
"scripts": {
  "build": "tsc --project tsconfig.json && tscpaths --project tsconfig.json",
}
```

## Building only the types
You can also setup a seperate tsconfig file just for types like `tsconfig.types.json` if you are also compiling with Babel.
```json
// tsconfig.types.json
{
  "extends": "./tsconfig",
  "compilerOptions": {
    "module": "amd",
    "outDir": "dist",
    "rootDir": "./src",
    "declaration": true,
    "declarationMap": false,
    "isolatedModules": false,
    "noEmit": false,
    "allowJs": false,
    "emitDeclarationOnly": true
  },
  "exclude": ["**/*.test.ts"]
}
```
And then target that
```json
"scripts": {
  "build:types": "tsc --project tsconfig.types.json && tscpaths -project tsconfig.types.json",
}
```

Your final build script might look like
```json
"scripts": {
  "build": "yarn build:commonjs && yarn build:types",
}
```

## Options
| flag         | description                                                                          |
| ------------ | ------------------------------------------------------------------------------------ |
| -p --project | project configuration file (tsconfig.json)                                           |
| -s --src     | source code root directory (overrides the tsconfig provided)                         |
| -o --out     | output directory of transpiled code (tsc --outDir) (overrides the tsconfig provided) |
| -v --verbose | console.log all the events                                                           |

# Disclaimer
This is not a mature project yet. Pull Requests are welcome!

It works for my setup so far.

It may not work correctly if your setup is too complicated, so please do some testing before pushing it to production!!!


# Changelog

>  You need to provide -s (--src) and -o (--out), because it's hard to predict source and output paths based on tsconfig.json.
>  
>  I've tried a little and failed. :(

The above is no longer neccesary <-- got you fam: @jonkwheeler