# 1nstall

> Install a package as if it was the only package

Latest version **0.4.0** (published 2023-02-21) · 0 weekly downloads

## Install

```sh
npm install 1nstall
pnpm add 1nstall
yarn add 1nstall
bun add 1nstall
```

Provides the commands `one`, `1nstall`.

## Health

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

Positive: esm support; no vulnerabilities.

Warnings: low downloads; no types; low quality score; pre 1.0.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 0.4.0 |
| Published | 2023-02-21 |
| First published | 2016-10-28 |
| Weekly downloads | 0 |
| TypeScript types | none |
| Module format | ESM + CommonJS |
| Dependencies | 3 |
| Unpacked size | 10.6 KB |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 1 |
| Maintainers | laggingreflex |

## Links

- npm: https://www.npmjs.com/package/1nstall
- Repository: https://github.com/laggingreflex/1nstall
- Homepage: https://github.com/laggingreflex/1nstall#readme
- Issues: https://github.com/laggingreflex/1nstall/issues
- npm.io page: https://npm.io/package/1nstall

## Dependencies (3)

- [yargs](https://npm.io/package/yargs.md) ^16.0.3
- [fs-extra](https://npm.io/package/fs-extra.md) ^9.0.1
- [enquire-simple](https://npm.io/package/enquire-simple.md) ^2.4.0

## Recent versions

- 0.4.0 (latest) — 2023-02-21
- 0.3.0 — 2020-10-06
- 0.2.2 — 2018-05-20
- 0.2.1 — 2018-03-12
- 0.1.0 — 2017-01-18
- 0.0.0 — 2016-10-28

## README

# 1nstall
[![npm](https://img.shields.io/npm/v/1nstall.svg)](https://www.npmjs.com/package/1nstall)

Install a package as if it was the only package.

## Why?

Does installing a new dependency take a lot of time when you have a lot of `node_modules` already installed?

## How?

It installs the dependency it in a temporary location then it moves\* it to your project, along with `.bin`s, and updated your `package.json`.

## Usage

```
npm install -g 1nstall
```
```
one jquery
# or
one npm --saveDev jquery
```

## Caveats

* It's only beneficial when the installing package is actually smaller (dependencies included) than your project. Which usually is the case.

* It only updates `package.json` not `package-lock.json` file.

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