open-index/open-npm huggingface dataset:
npm package: @jsumners/git-user-config
Description: Configure your git user for current repo
Author: palortoff
Latest version: 2.3.0

Do you use different user names and/or email for your github projects, work
projects, private personal projects?

Then you use ``git config`` a lot.

With ``git-user-config`` you can save these different users globally and
configure a new repo with a single command using record identifiers.
No more misspelled email addresses and user names...

# Install

`npm install -g git-user-config`

# Add User record for later use

`git-user-config --add`

Then follow instructions

```sh
Add new user record

Identifier: personal

Enter property names like `user.email`
Property name (none to end): user.name
Value: Joe Schmo
Property name (none to end): user.email
Value: joe@example.com
Property name (none to end):

record saved
```

# Configure git repo to use user record

`git-user-config --set user1`

This will call `git config --local` for each property of the `user1`
configuration.

````
$ git config -l | grep user
user.name=user 1
user.email=user_1@domain.com
````

# List all user records

    git-user-config --list

````
{
  "user1": {
    "user.name": "user 1",
    "user.email": "user_1@domain.com"
  },
  "user2": {
    "user.name": "user 2",
    "user.email": "user_2@domain.com"
  }
}
````

# Update a user record

`git-user-config --update user1`

This will interactively allow updating of the `user1` record. The process
works the same as `--add user1`. Any existing properties specified will be
overwritten, or removed if the new value is `~del~`, and new properties will
be merged in.

# Remove a user record

`git-user-config --remove user1`
npm package: @jsumners/node-skel
Description: A simple CLI utility to dump some skeleton files into a new Node project
Author: James Sumners
Latest version: 2.0.1

# node-skel

This is a simple CLI tool to initialize a new node project with some common
files, `npm` scripts, and dependencies.

By default the following will be added:

+ A `.editorconfig` file
+ A `.gitignore` file
+ A `.travis.yml` file
+ Development dependences: `pre-commit`, `snazzy`, `standard` and `tap`
+ Scripts for linting and testing
+ Pre-commit hooks for linting and testing

## Install and Usage

```sh
$ npm install -g @jsumners/node-skel
$ mkdir foo-project
$ cd foo-project
$ npm init
$ nskel
```

To learn about the available options, run `nskel run --help`.

> ### Note
> This utility is meant to be run *directly after* `npm init`.
> It will *overwrite* any "scripts" or "precommit" properties in the
> present `package.json` file, and any present dot files.

## License

[MIT License](http://jsumners.mit-license.org/)
npm package: @jsumners/require-self-ref
Description: Solves the relative path problem in Node.js by allowing a require call to reference the current package
Author: Patrick Steele-Idem
Latest version: 3.0.1

@jsumners/require-self-ref
================

**Fork Notice:** this is a fork of the [original require-self-ref][original].
This fork removes production dependencies so that it is a fully self-contained
module. Any issues with *this fork* should **not** be directed at the upstream
project.

Solves the relative path problem in Node.js by allowing the target module argument of a `require` call to be relative to the root directory of the containing package:

For example:

Given a JavaScript module at `my-package/src/some/deeply/nested/path/foo/index.js` that needs to require `my-package/src/util/bar.js`:


Without `require-self-ref`:

```javascript
require('../../../../../../util/bar')
```

:confused:

And _with_ `require-self-ref` installed:

```javascript
require('~/src/util/bar')
```

:smile:

[original]: https://github.com/patrick-steele-idem/require-self-ref

# Installation

```bash
npm install @jsumners/require-self-ref
```

# Usage

At the top of the main entry for your application add the following line:

```javascript
require('@jsumners/require-self-ref')
```

# Important

- Your package must have a `package.json` file at the root
- ***Use at your own risk*** (this package monkey-patches the Node.js require system and it depends on internals of Node.js that may change in the future)
- Compatible with all versions of Node.js

# Related projects:

- [app-module-path](https://github.com/patrick-steele-idem/app-module-path-node) - Simple module to add additional directories to the Node module search for top-level app modules
- [wavy](https://github.com/kolodny/wavy) - Similar to this package, but requires a `postinstall` script and symbolic links

# License

MIT