open-index/open-npm huggingface dataset:
npm package: @lenna-proj/lenna-cli
Description: Command line interface to run algorithms on images.
Latest version: 0.3.1

# lenna-cli
[![lenna-cli](https://snapcraft.io/lenna-cli/badge.svg)](https://snapcraft.io/lenna-cli)
[![Crates.io](https://img.shields.io/crates/v/lenna_cli)](https://crates.io/crates/lenna_cli)
[![dependency status](https://deps.rs/repo/github/lenna-project/lenna-cli/status.svg)](https://deps.rs/repo/github/lenna-project/lenna-cli)

Lenna is a library for image processing algorithms and apps.

This is the Command Line Interface for [Lenna](https://lenna.app) based on [lenna_core](https://github.com/lenna-project/lenna-core).

[![asciicast](https://asciinema.org/a/420516.svg)](https://asciinema.org/a/420516)

![Lenna CLI](https://www.plantuml.com/plantuml/proxy?cache=no&src=https://raw.githubusercontent.com/lenna-project/lenna-cli/main/docs/uml/cli.puml)

## 🐰 quickstart

```bash
cargo build
```

## ✂️ copy plugins

Here are some [plugins](https://github.com/lenna-project/lenna-plugins).
After the plugins are built, they can be copied and used with lenne-cli.

```bash
mkdir plugins
cp ../lenna-plugins/target/release/lib*.so plugins/
```

## 🔧 config

Create a file called lenna.yml.

```yaml
pipeline:
  - id: resize
    width: 500
    height: 500
  - id: canny
    low: 50.0
    high: 100.0
  - id: blur
    sigma: 1.5
```

Id is the plugin, the other attributes are the parameter for the plugin.

## 👻 run

```bash
cargo run --features="libloading" -- lenna.png -o lenna_out.png -c lenna.yml
```

![Run](docs/images/run.gif)

## install

Install using snapcraft.

```bash
snapcraft
sudo snap install lenna-cli_*.snap --devmode --dangerous
lenna-cli --help
lenna-cli lenna.png --config lenna.yml --output out.png --plugins /snap/lenna-cli/current/plugins
```

## 🐍 build python bindings

Create a virtual environment for python and install lenna-cli using pip.

```bash
virtualenv -p python3 .venv
source .venv/bin/activate
pip install .
python src/python/test.py
```

```python
import lenna_cli
lennaCli = lenna_cli.LennaCli()
print(lennaCli.plugins())
```

### jupyter

You can test the python bindings in a [jupyter notebook](https://github.com/lenna-project/jupyter/blob/main/content/lenna-cli.ipynb).

## 📜 License

This software is licensed under the [MIT](https://github.com/lenna-project/lenna-cli/blob/main/LICENSE) © [lenna-project](https://github.com/lenna-project).
npm package: @lenna-proj/lenna-web
Description: Online version of the lenna image processing app.
Author: chriamue
Latest version: 0.0.7

# lenna-web

Online version of the lenna image processing app.

[![codecov](https://codecov.io/gh/lenna-project/lenna-web/branch/main/graph/badge.svg?token=1FY0D7K622)](https://codecov.io/gh/lenna-project/lenna-web)
<a href="https://observatory.mozilla.org/analyze/lenna.app" title="Latest Results"><img src="https://img.shields.io/mozilla-observatory/grade/lenna.app" alt="Mozilla HTTP Observatory Grade"></a>
<a href="https://www.chromatic.com/library?appId=612a8a0a410daf003aa230af">
    <img src="https://user-images.githubusercontent.com/321738/63501763-88dbf600-c4cc-11e9-96cd-94adadc2fd72.png" alt="Storybook" height="24" />
</a>

[https://lenna.app](https://lenna.app)
npm package: @lennardvdberg/eslint-config-react-lennard
Description: My ESLint configuration for React
Author: Lennard van den Berg
Latest version: 3.0.0

# @lennardvdberg/eslint-config-react-lennard

[![npm version](https://badge.fury.io/js/@lennardvdberg%2Feslint-config-react-lennard.svg)](https://badge.fury.io/js/@lennardvdberg%2Feslint-config-react-lennard)

An opinionated default [ESLint](https://github.com/eslint/eslint) + [Typescript](https://github.com/microsoft/TypeScript) + [Prettier](https://github.com/prettier/prettier) configuration for [React](https://github.com/facebook/react). Make Eslint and prettier work with only one package installation.

## Usage

```sh
yarn add @lennardvdberg/eslint-config-react-lennard --dev
```

The [`example`](/example) folder contains the files required to use this configuration. Alternatively, you can also add the ESLint, Prettier and Typescript configuration manually:

1. Create an `.eslintrc.js` file in your project root:

```js
module.exports = {
  extends: 'eslint-config-react-lennard',
  rules: {
    // override or add additional rules here
  },
}
```

2. In `tsconfig.json` (if you want to use my base TS configuration):

```json
{
  "extends": "@lennardvdberg/eslint-config-react-lennard/tsconfig.base"
}
```

3. Create a .prettierrc.js file in your project root and add:

```js
const prettier = require('@lennardvdberg/eslint-config-react-lennard/prettier')

// You can also overwrite some keys in this config

module.exports = prettier
```

Alternatively, in your package.json file add the following key:

```json
{
  "prettier": "@lennardvdberg/eslint-config-react-lennard/prettier"
}
```

4. Also recommended to add an `.editorconfig` file at the project root:

```
root = true

[*]
indent_style = tab
indent_size = 2
charset = utf-8
trim_trailing_whitespace = true
insert_final_newline = true
```

5. If you're using VSCode, you can copy the files in the .vscode folder to enable "Format on save" and use the ESLint plugin for formatting.

6. This package is meant to be used as an opinionated standalone. It includes both `eslint` and `prettier`. With these you can for example use them in `scripts` in `package.json`:

```json
{
  "scripts": {
    "lint": "eslint ."
  }
}
```

## Releases

Pushes to the 'main' branch are automatically published to NPM. This is done via [semantic-release](https://github.com/semantic-release/semantic-release) which runs on CircleCI, see the [CircleCI config](/.circleci/config.yml). Semantic-release uses the commit messages to check whether a release is necessary and what the version bump will be, see [How does CircleCI work?](https://github.com/semantic-release/semantic-release#how-does-it-work).
npm package: @lennartki/n8n-nodes-multitenantmicrosoft
Description: This is an n8n community node. It lets you use _app/service name_ in your n8n workflows.
Latest version: 0.1.3

# @lennartki/n8n-nodes-multitenantmicrosoft

This is an n8n community node. It lets you use _app/service name_ in your n8n workflows.

_App/service name_ is _one or two sentences describing the service this node integrates with_.

[n8n](https://n8n.io/) is a [fair-code licensed](https://docs.n8n.io/sustainable-use-license/) workflow automation platform.

[Installation](#installation)
[Operations](#operations)
[Credentials](#credentials)
[Compatibility](#compatibility)
[Usage](#usage)
[Resources](#resources)
[Version history](#version-history)

## Installation

Follow the [installation guide](https://docs.n8n.io/integrations/community-nodes/installation/) in the n8n community nodes documentation.

## Operations

_List the operations supported by your node._

## Credentials

_If users need to authenticate with the app/service, provide details here. You should include prerequisites (such as signing up with the service), available authentication methods, and how to set them up._

## Compatibility

_State the minimum n8n version, as well as which versions you test against. You can also include any known version incompatibility issues._

## Usage

_This is an optional section. Use it to help users with any difficult or confusing aspects of the node._

_By the time users are looking for community nodes, they probably already know n8n basics. But if you expect new users, you can link to the [Try it out](https://docs.n8n.io/try-it-out/) documentation to help them get started._

## Resources

* [n8n community nodes documentation](https://docs.n8n.io/integrations/#community-nodes)
* _Link to app/service documentation._

## Version history

_This is another optional section. If your node has multiple versions, include a short description of available versions and what changed, as well as any compatibility impact._
npm package: @lennartki/n8n-nodes-postnl
Description: n8n node to connect with PostNL API
Author: lennartki
Latest version: 0.1.0

# @lennartki/n8n-nodes-postnl

![n8n logo](n8n.png)

Project for [**PostNL OpenAPI spec**](https://api.postnl.nl/)
using [**devlikeapro/n8n-openapi-node**](https://github.com/devlikeapro/n8n-openapi-node)



<!-- toc -->

- [Run PostNL n8n node locally](#run-postnl-n8n-node-locally)
  * [NodeJS](#nodejs)
  * [Install n8n](#install-n8n)
  * [Start n8n](#start-n8n)
  * [Build and link the project](#build-and-link-the-project)
  * [Add node to n8n](#add-node-to-n8n)
  * [Start n8n again](#start-n8n-again)
  * [Add PostNL Node to new workflow](#add-postnl-node-to-new-workflow)
- [Modify Project](#modify-project)
  * [Test Project Locally](#test-project-locally)
  * [Publish project](#publish-project)

<!-- tocstop -->

# Run PostNL n8n node locally
Before start modifying the project, we kindly recommend
to run the PostNL locally.

## NodeJS
Make sure you're using Node.js > 20 (we're using [nvm](https://github.com/nvm-sh/nvm)):
```bash
nvm install v22.8
nvm use v22.8
```

## Install n8n 
```bash
npm install n8n -g
```

## Start n8n
```bash
n8n --version
n8n start
```
Open [http://localhost:5678](http://localhost:5678) in your browser and configure it

## Build and link the project
```bash
npm install
npm run test
npm run build
npm link
```

## Add node to n8n
```bash
cd ~/.n8n
mkdir -p custom
cd custom
npm init # press Enter for all questions
npm link @lennartki/n8n-nodes-postnl
```

## Start n8n again
```bash
n8n start
```

## Add PostNL Node to new workflow
Find `PostNL` in the node list and add it to your workflow

![workflow](./images/workflow.png)
![screenshot](./images/screenshot.png)

## Test Project Locally

```bash
npm install
npm run test
npm run build
npm link
```

Add node to n8n:
```bash
cd ~/.n8n
mkdir -p custom
cd custom
npm init # press Enter for all questions
npm link @lennartki/n8n-nodes-postnl
```

Start n8n:
```bash
n8n start
```

## Publish project
1. Add your `NPM_TOKEN` in GitHub Actions
2. Push change
3. Create a new GitHub Release, `1.0.0` in your project
4. Install your node in n8n: `@{yourgithubname}/n8n-nodes-{yournode}`
npm package: @lenne.tech/lenne-nuxt-gql
Description: Nuxt graphql module of @lenne.tech
Latest version: 1.0.3

<!--
Get your module up and running quickly.

Find and replace all on all files (CMD+SHIFT+F):
- Name: My Module
- Package name: @lenne.tech/lenne-nuxt-gql
- Description: My new Nuxt module
-->

# @lenne.tech/lenne-nuxt-gql

[![npm version][npm-version-src]][npm-version-href]
[![npm downloads][npm-downloads-src]][npm-downloads-href]
[![License][license-src]][license-href]
[![Nuxt][nuxt-src]][nuxt-href]

My new Nuxt module for doing amazing things.

- [✨ &nbsp;Release Notes](/CHANGELOG.md)
<!-- - [🏀 Online playground](https://stackblitz.com/github/your-org/@lenne.tech/lenne-nuxt-gql?file=playground%2Fapp.vue) -->
<!-- - [📖 &nbsp;Documentation](https://example.com) -->

## Features

<!-- Highlight some of the features your module provide here -->
- ⛰ &nbsp;Foo
- 🚠 &nbsp;Bar
- 🌲 &nbsp;Baz

## Quick Setup

1. Add `@lenne.tech/lenne-nuxt-gql` dependency to your project

```bash
# Using pnpm
pnpm add -D @lenne.tech/lenne-nuxt-gql

# Using yarn
yarn add --dev @lenne.tech/lenne-nuxt-gql

# Using npm
npm install --save-dev @lenne.tech/lenne-nuxt-gql
```

2. Add `@lenne.tech/lenne-nuxt-gql` to the `modules` section of `nuxt.config.ts`

```js
export default defineNuxtConfig({
  modules: [
    '@lenne.tech/lenne-nuxt-gql'
  ]
})
```

That's it! You can now use My Module in your Nuxt app ✨

## Development

```bash
# Install dependencies
npm install

# Generate type stubs
npm run dev:prepare

# Develop with the playground
npm run dev

# Build the playground
npm run dev:build

# Run ESLint
npm run lint

# Run Vitest
npm run test
npm run test:watch

# Release new version
npm run release
```

<!-- Badges -->
[npm-version-src]: https://img.shields.io/npm/v/@lenne.tech/lenne-nuxt-gql/latest.svg?style=flat&colorA=18181B&colorB=28CF8D
[npm-version-href]: https://npmjs.com/package/@lenne.tech/lenne-nuxt-gql

[npm-downloads-src]: https://img.shields.io/npm/dm/@lenne.tech/lenne-nuxt-gql.svg?style=flat&colorA=18181B&colorB=28CF8D
[npm-downloads-href]: https://npmjs.com/package/@lenne.tech/lenne-nuxt-gql

[license-src]: https://img.shields.io/npm/l/@lenne.tech/lenne-nuxt-gql.svg?style=flat&colorA=18181B&colorB=28CF8D
[license-href]: https://npmjs.com/package/@lenne.tech/lenne-nuxt-gql

[nuxt-src]: https://img.shields.io/badge/Nuxt-18181B?logo=nuxt.js
[nuxt-href]: https://nuxt.com
npm package: @lenne.tech/ng-base
Description: Angular library with basic elements and for communication with the lenne.Tech Nest Server
Author: lenne.Tech
Latest version: 18.1.2

# Angular Base

This is the base library of [lenne.Tech](https://lenne.tech) for Angular.

## Description

This library contains all the basics to start a new project in combination with the [lenne.Tech Nest Server](https://github.com/lenneTech/nest-server#lennetech-nest-server):

- GraphQL service and elements for easy communication with GraphQL API (via Models)
- Standard Model with methods for mapping, cloning and comparing models
- Basic User Model with basic rights handling
- Loading Service for the subscription of loading processes
- Storage Service for comfortable saving of data in local storage
- GraphQL service and elements for easy communication with GraphQL API (via Models)
- Authentication service for user registration
- and much more

For setting up a new project we recommend our [Angular Starter](https://github.com/lenneTech/angular-starter), which already contains this library and also includes a few sample elements as templates.

## Requirements

- [Angular Project (Version 11)](https://angular.io/tutorial/toh-pt0)

## Integration into an Angular project

Installation

```bash
cd path/to/your/angular-project
npm i @lenne.tech/ng-graphql-client
```

Integration in your App Module (`src/app/app.module.ts`):

```typescript
import { GraphQLModule } from '@lenne.tech/ng-graphql-client'
@NgModule({
  imports: [
      GraphQLModule.forRoot({
        apiUrl: 'https://url.to-your.domain/api',
        authGuardRedirectUrl: '/path/to/login', // optional (default: '/auth')
        prefix: 'prefixForLocalStorageKeys', // optional (default: '')
        scrollDetectionOffset: 200, // should be >= scrollOffset, optional (default: 200)
        scrollOffset: 100, // optional (default: 100)
        storageType: 'local' as StorageType, // optional (default: 'local')
        version: '0.1', // to set version for storage keys, optional (default: '')
      })
  ],
})
```

## Usage

Description follows ...

## Thanks

Many thanks to the developers of [Angular](https://angular.io/), [Apollo Angular](https://apollo-angular.com/)
and all the developers whose packages are used here.

## License

MIT - see LICENSE
npm package: @lenne.tech/ng-graphql-client
Description: An Angular Module for communicate with an GraphQL Server.
Author: Pascal Klesse
Latest version: 0.1.7
Deprecated: @lenne.tech/ng-graphql-client is no longer supported, please use @lenne.tech/ng-base instead.

# @lenne.tech/ng-graphql-client

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 11.0.4.

## Code scaffolding

Run `ng generate component component-name --project graphql-client` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project graphql-client`.
> Note: Don't forget to add `--project graphql-client` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build graphql-client` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build graphql-client`, go to the dist folder `cd dist/graphql-client` and run `npm publish`.

## Running unit tests

Run `ng test graphql-client` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI Overview and Command Reference](https://angular.io/cli) page.
npm package: @lenne.tech/npm-package-helper
Description: Helper for editing npm package files
Author: Kai Haase
Latest version: 0.0.12

# Npm package helper

[lenne.Tech](https://github.com/lenneTech) helper for handling npm packages.

For example, the versions of package.json and package-lock.json can be synchronized very easily.

[![License](https://img.shields.io/github/license/lenneTech/npm-package-helper)](/LICENSE) [![CircleCI](https://circleci.com/gh/lenneTech/npm-package-helper/tree/master.svg?style=shield)](https://circleci.com/gh/lenneTech/npm-package-helper/tree/master)
[![Dependency Status](https://david-dm.org/lenneTech/npm-package-helper.svg)](https://david-dm.org/lenneTech/npm-package-helper) [![devDependency Status](https://david-dm.org/lenneTech/npm-package-helper/dev-status.svg)](https://david-dm.org/lenneTech/npm-package-helper?type=dev)

<!--
[![GitHub forks](https://img.shields.io/github/forks/lenneTech/npm-package-helper)](https://github.com/lenneTech/npm-package-helper/fork) [![GitHub stars](https://img.shields.io/github/stars/lenneTech/npm-package-helper)](https://github.com/lenneTech/npm-package-helper)
-->

## Installation

```
$ npm install --save-dev @lenne.tech/npm-package-helper
```

## Usage

After installing this package, the root directory of the project should contain the following script, which synchronizes the package.json and package-lock.json versions:

`extras/sync-version.ts`

```typescript
import NpmPackageHelper from '@lenne.tech/npm-package-helper';
import { join } from 'path';

// Sync version of package.json and package-lock.json
const run = () => {
  // Init
  const nph = NpmPackageHelper;
  const dir = process.cwd();

  // Set highest version
  nph
    .setHighestVersion([
      nph.getFileData(join(dir, 'package-lock.json')),
      nph.getFileData(join(dir, 'package.json'))
    ])
    .then(version => {
      // Log version
      console.log(version);
    });
};
run();
```

This script can be used by husky, for example:

`package.json`

```json5
{
  // ...
  husky: {
    hooks: {
      'pre-commit': 'ts-node extras/sync-version.ts && pretty-quick --staged',
      'pre-push': 'npm run lint && npm run test'
    }
  }
  // ...
}
```

## License

MIT - see LICENSE
npm package: @lenne.tech/nuxt-base
Description: Nuxt base module of @lenne.tech
Author: lenne.Tech
Latest version: 4.0.3

# @lenne.tech/nuxt-base

[![npm version][npm-version-src]][npm-version-href]
[![npm downloads][npm-downloads-src]][npm-downloads-href]
[![License][license-src]][license-href]
[![Nuxt][nuxt-src]][nuxt-href]

@lenne.tech/nuxt-base had some amazing features for easy initialize nuxt applications.

- [✨ &nbsp;Release Notes](/CHANGELOG.md)
<!-- - [🏀 Online playground](https://stackblitz.com/github/your-org/@lenne.tech/nuxt-base?file=playground%2Fapp.vue) -->
<!-- - [📖 &nbsp;Documentation](https://example.com) -->

## Features

<!-- Highlight some of the features your module provide here -->
- &nbsp;GraphQL codegen
- &nbsp;Easy graphql syntax

## Quick Setup

1. Add `@lenne.tech/nuxt-base` dependency to your project

```bash
# Using npm
npm install -D @lenne.tech/nuxt-base

# Using yarn
yarn add --dev @lenne.tech/nuxt-base

# Using npm
npm install --save-dev @lenne.tech/nuxt-base
```

2. Add `@lenne.tech/nuxt-base` to the `modules` section of `nuxt.config.ts`

```js
export default defineNuxtConfig({
  modules: [
    '@lenne.tech/nuxt-base'
  ]
})
```

That's it! You can now use @lenne.tech/nuxt-base in your Nuxt app ✨

## Development

```bash
# Install dependencies
npm install

# Generate type stubs
npm run dev:prepare

# Develop with the playground
npm run dev

# Build the playground
npm run dev:build

# Run ESLint
npm run lint

# Run Vitest
npm run test
npm run test:watch

# Release new version
npm run release
```

<!-- Badges -->
[npm-version-src]: https://img.shields.io/npm/v/@lenne.tech/nuxt-base/latest.svg?style=flat&colorA=18181B&colorB=28CF8D
[npm-version-href]: https://npmjs.com/package/@lenne.tech/nuxt-base

[npm-downloads-src]: https://img.shields.io/npm/dm/@lenne.tech/nuxt-base.svg?style=flat&colorA=18181B&colorB=28CF8D
[npm-downloads-href]: https://npmjs.com/package/@lenne.tech/nuxt-base

[license-src]: https://img.shields.io/npm/l/@lenne.tech/nuxt-base.svg?style=flat&colorA=18181B&colorB=28CF8D
[license-href]: https://npmjs.com/package/@lenne.tech/nuxt-base

[nuxt-src]: https://img.shields.io/badge/Nuxt-18181B?logo=nuxt.js
[nuxt-href]: https://nuxt.com
npm package: @lenne.tech/nuxt-base-starter
Description: Starter to generate a configured environment with VueJS, Nuxt, Tailwind, Eslint, @lenne.tech/nuxt-base, Storybook, Unit Tests, Cypress etc.
Author: lenne.Tech GmbH
Latest version: 0.0.9
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# Nuxt Starter
This is a starter template to create a Nuxt 3 development environment including Tailwind, Pinia, VueUse, Nuxt Base, Eslint and optionally Cypress, Unit Tests and Storybook.

Just run the following command to create your Nuxt environment:

```bash
npx @lenne.tech/nuxt-base-starter my-awesome-project
```
## Options
To add Tests and storybook to your environment you can add the following flags:
```bash
npx @lenne.tech/nuxt-base-starter --tests --storybook my-awesome-project
```
npm package: @lennon/ttl-cache
Description: Simple ttl cache
Author: Bence Dányi
Latest version: 1.0.0

# ttl-cache

> in-memory ttl cache. that's it

## install

```sh
$ npm i @lennon/ttl-cache
```

## usage

```js
import c from '@lennon/ttl-cache';

const cache = c();
cache.set('foo', 'bar');
console.log(cache.get('foo'));
```

## api

### `cache([opts])`

create cache that keep items for `opts.ttl || 300000` ms, and does cleanup
every `opts.interval || 60000` ms.

### `cache.get(key)`

get item by key, or null if expired or missing

### `cache.set(key, value)`

set item by key

### `cache.length`

get current cache size (might contain expired items too)

## license

MIT
npm package: @lennonsaves/typed-config
Description: ## Why? Configuration management is hard.   * Multiple environments mean multiple `.env` files   * `.env` files are a list of keys and values, they have no structure   * No runtime validation (you can check for existence of environment variables, but not 
Latest version: 0.1.25

# `typed-config`

## Why?
Configuration management is hard.
  * Multiple environments mean multiple `.env` files
  * `.env` files are a list of keys and values, they have no structure
  * No runtime validation (you can check for existence of environment variables, but not much more (easily))
  * No dev time help (autosuggestions)
  * How to populate secrets secrets safely (and for multiple environments, possibly with different encyrption keys and in isolated environments)?
  * How to allow developers to specify secrets without having access to these secrets?

  ## How?

    * Create a `./config` directory in your project root
    * Add a `default.yml` in this folder and populate it with your configuration
      ```yaml
      # example for `bunyan` logger config
      logger:
        name: my-awesome-project
        level: info
      ```
    * Create a class that represents your configuration using the amazing `class-validator to define validations
      ```typescript
      import { IsDefined } from 'class-validator'
      import { LoggerOptions } from 'bunyan'
      export class Config {
        @IsDefined()
        logger: LoggerOptions
      }
      ```
    * In the `index.ts` (or whatever your `main` file is) load the config
    ```typescript
    import { loadConfig } from '@barath/typed-config'
    import { Config } from './lib/config'
    import bunyan from 'bunyan'
    export const config = loadConfig(Config)
    export const logger = bunyan.createLogger(config.logger)
    
    logger.info('hello world')
    ```
npm package: @lennym/caseify
Description: Browserify transform to ensure all dependencies exist in a case-sensitive environment
Author: justin j. moses
Latest version: 0.2.0

Caseify
=======
Browserify transform to ensure all dependencies exist in a case-sensitive environment. Checks that all `require` expressions with relative paths point to a file that can be found using a case preserving string match.

Useful for detecting issues in case sensitive module naming on case-insensitive dev machines (such as OS X and WinX) that end up causing issues on Linux based Continuous Integration machines.

Installation
-------

* `npm install --save-dev caseify` install as dev dependency
* add `'caseify'` as a browserify transform via
```json
    {
      "browserify": {
        "transform": [ "caseify" ]
      }
    }
```
or if using Gulp or Grunt, simply add `'casefiy'` to your list of transforms.


Options
-----

To configure how caseify works, add setting in your project's `package.json` file under `caseify`.

* `relativePaths`: Default `false` - show file paths as relative to the current working directory

* `throwOnError`: Default `fasle` - throw a fatal error if an invalid module is found. This is instead of the default behaviour which emits an error on the browserify stream. Note: this will occur before browserify has processed the file and interrupt it immediately.


eg. `package.json`

```json
 ...
 "devDependencies": {
     "caseify": "~0.1"
 },
 "caseify": {
    "relativePaths": true,
    "throwOnError": true
  },
  ...
```

Example
------

Within this directory structure:

    moduleA.js
    |-- deps/moduleB.js
    |-- deps/moduleC.js

if __moduleA.js__ contains:
```javascript
var moduleB = require('./deps/moduleb');
```

running: `browserify -t caseify module*.js > module.bundle.js`

causes this output:

    Caseify: /Users/jmoses/example/moduleA.js module ./deps/moduleb not found in case-sensitive environment
npm package: @lennym/ciaudit
Description: Wrapper for npm audit to allow configurable vlun levels
Latest version: 2.0.1

# ciaudit

Wrapper for npm audit to allow configurable severity levels and support ignore lists for specific advisories.

## Install

To install into a project:

```
$ npm install --save-dev @lennym/ciaudit
```

If installed in a project then the recommended usage is to add a line to the `scripts` section of package.json:

```
"scripts": {
  ...
  "audit": "ciaudit"
}
```

and then run:

```
$ npm run audit
```

## Basic usage

Define a base severity level by passing a flag of `--low`, `--moderate`, `--high` or `--critical`. Default: `low`

```
# as an installed module
$ ciaudit [--moderate | --high | --critical]
# with npx
$ npx @lennym/ciaudit [--moderate | --high | --critical]
```

This process will output a JSON formatted report and will exit with a non-zero exit code if any non-ignored advisories are detected.

### Other options

* `--production` - ignore dev dependencies when running audit (Default: `false`)

Note: `--production` will be inherited from npm CLI, so if running via an npm script `npm run audit --production` will be equivalent to `npm run audit -- --production`

* `--ignorefile` - use specified file to load ignore list (Default: `./.auditignore`)

By default an installed version of `@npmcli/arborist` is used to perform the audit, and so is not dependent on the locally installed npm runtime. However, this can be overridden by passing a `--local` flag.

* `--local` - use locally installed npm version to perform audit (Default: `false`)

## Ignore file

Advisories can be ignore by listing in an ignore file - default `.auditignore`.

Entries in the ignore file can be defined based on source, module name, and install path. Install paths are separated by `>` and can include wildcards (`*`).

```
# ignore advisory with source id 1005560
1005560

# ignore advisories relating to package `node-fetch`
node-fetch

# ignore advisories in child/descendant dependencies of `webpack`
webpack>* 
```

### Advanced usage

Ignore file entries can be combined by using a `&&` separator. In this case _all_ conditions must be met for the advisory to be ignored.

In the following example, advisory 1006947 (related to the `glob-parent` module) is ignored only when it appears as a descendant of `webpack`.

```
# ignore 1006947 as a descendant of webpack
1006947 && webpack>*
```

### Note on path matching

Due to [a bug in `npm`](https://github.com/npm/cli/issues/4366) at time of writing, some reported install paths may be incomplete and not include a complete set of ancestor dependencies where a module with an advisory has multiple install paths with a common ancestor.

## Updating from v1.x

v2.0.0 is a total ground-up rewrite of the module to solve a different set of problems that have emerged as `npm audit` has developed and matured.

As such it should be considered a complete breaking change, and a from-scratch reimplementation is recommended.
npm package: @lennym/commit
Description: Simple API for committing file changes to github
Author: Leonard Martin
Latest version: 1.0.1

# @lennym/commit

API for committing file changes to github

## Usage

To write content to a file on the default branch:

```js
const Git = require('@lennym/commit');

const git = Git({
  repo: 'lennym/test-repo',
  token: 'YOUR_GITHUB_ACCESS_TOKEN'
});

git
  .add('file.txt', 'File content')
  .commit('Set file content')
  .push()
  .then(() => console.log('All done'));
```

### Branches

To write to a branch other than the default branch for the repo:

```js
const git = Git({
  repo: 'lennym/test-repo',
  token: '...',
  branch: 'development'
});

git
  .add('file.txt', 'File content')
  .commit('Set file content')
  .push()
  .then(() => console.log('All done'));
```

To create a new branch:

```js
const git = Git({
  repo: 'lennym/test-repo',
  token: '...'
});

git
  .branch('my-new-branch')
  .add('file.txt', 'File content')
  .commit('Set file content')
  .push()
  .then(() => console.log('All done'));
```

### Updating multiple files

To update multiple files in one commit:

```js
const git = Git({
  repo: 'lennym/test-repo',
  token: '...'
});

git
  .add('file1.txt', 'File 1 content')
  .add('file2.txt', 'File 2 content')
  .commit('Set multiple file content')
  .push()
  .then(() => console.log('All done'));
```

To update multiple files in multiple commits:

```js
const git = Git({
  repo: 'lennym/test-repo',
  token: '...'
});

git
  .add('file1.txt', 'File 1 content')
  .commit('Update file 1')
  .add('file2.txt', 'File 2 content')
  .commit('Update file 2')
  .push()
  .then(() => console.log('All done'));
```

### Non-text files

To add a non-text file, pass a `Buffer` instead of a string to `add`:

```js
const img = fs.readFileSync('./some-image.png');

const git = Git({
  repo: 'lennym/test-repo',
  token: '...'
});

git
  .add('image.png', img)
  .commit('Add image file')
  .push()
  .then(() => console.log('All done'));
```

## Other actions

### Get the hash of the latest commit

```js
const git = Git({
  repo: 'lennym/test-repo',
  token: '...'
});

git.head()
  .then(sha => console.log(sha));
```
npm package: @lennym/drone-deploy
Description: ## Running
Latest version: 1.0.2

# drone-deploy

## Running

Install dependencies:

```
npm install
```

Set the following environment variables:

* `GITHUB_ORG`
* `GITHUB_REPOS` - comma separated list of repo names
* `DRONE_SERVER`
* `DRONE_TOKEN`
* `DEPLOY_ENVIRONMENTS` - comma separated list of environment names - defaults to `dev,preprod,prod`

Start the server:

```
npm start
```

Visit http://localhost:3000.