# friendlyquire

> wrap require to make package-root-relative requires nicer

Latest version **1.0.1** (published 2014-02-04) · MIT license · 0 weekly downloads

## Install

```sh
npm install friendlyquire
pnpm add friendlyquire
yarn add friendlyquire
bun add friendlyquire
```

## Health

**Score 15/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 1.0.1 |
| Published | 2014-02-04 |
| First published | 2014-02-04 |
| Weekly downloads | 0 |
| License | MIT |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 0 |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 1 |
| Author | Nathan Zadoks |
| Maintainers | nathan7 |
| Keywords | require, friendly |

## Links

- npm: https://www.npmjs.com/package/friendlyquire
- Repository: https://github.com/nathan7/friendlyquire
- Issues: https://github.com/nathan7/friendlyquire/issues
- npm.io page: https://npm.io/package/friendlyquire

## Recent versions

- 1.0.1 (latest) — 2014-02-04
- 1.0.0 — 2014-02-04

## README

# friendlyquire

  wrap require to make package-root-relative requires nicer

## Installation

    npm install --save friendlyquire

## Usage

  friendlyquire replaces regular require, and gives you `~` as a prefix to require something local. Just `~` refers to your package root.

```javascript
require = require('friendlyquire')(require)
var something = require('something')
  , localStuff = require('~/stuff')
```

## Is this a good idea?

  I haven't got the slightest clue.

---
_Source: https://npm.io/package/friendlyquire · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._