Catalog npm
PACKAGE EXPLORERView in registry

1nstall

npm

Install a package as if it was the only package

Versions collected6
Direct dependencies3From release 0.4.0
Last observed20 Oct, 18:34 UTC

README

Current package documentation

1nstall

npm

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 .bins, 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.

Downloads & popularity

Awaiting observations

No metric observations yet

Download counts and popularity will appear here as the collector receives them.

Versions 6

Collected releases
VersionPublishedDirect dependenciesOpen version
0.4.0Registry latest21 Feb 20233
0.3.06 Oct 20203
0.2.220 May 20187
0.2.112 Mar 20187
0.1.018 Jan 201715
0.0.028 Oct 201613

Package advisories

0
No matching advisories collected

This describes our collected data; it is not a security assessment.

Repository

PENDING
laggingreflex/1nstall

Shared repository data · GitHub

License detected in repository
Not collected

Metadata history

Meaningful changes
Current collected state Current

Observed since 20 Oct, 18:34 UTC

No superseded metadata states collected. Unchanged observations do not create new revisions.

Record identity

package:df83684486279efe6e2eac654fd33837984ca39e2acf7b0539f93fd4fc785b32