local-pkg
npmv1.2.1TypeScriptGet information on local packages.
Safe to adopt
Yes — local-pkg scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 112 days ago. 7 releases in the last 2 years.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- BMaintenance: grade B, Good.
Last published 112 days ago. 7 releases in the last 2 years.
- BWeight: grade B, Good.
Pulls in 8 transitive packages, about 1.1 MB installed (at least — some of the tree is still being crawled).
- ASupply chain: grade A, Excellent.
No install scripts, 2 maintainers, and a contained dependency surface.
- ALicense: grade A, Excellent.
MIT — permissive, with no copyleft found in the dependency tree.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding local-pkg to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Part of this dependency tree has not been crawled yet, so these figures are a lower bound rather than a final total.
Licenses in the dependency tree
Every license you inherit by installing local-pkg, not just its own. Check this before a legal review, not after.
Compatibility
- Node.js
- node >=14
- Module format
- ESM + CommonJS
- TypeScript
- Types included
- Install scripts
- None
Quick start
A usage example from the local-pkg README.
import {
getPackageInfo,
importModule,
isPackageExists,
resolveModule,
} from 'local-pkg'
isPackageExists('local-pkg') // true
isPackageExists('foo') // false
await getPackageInfo('local-pkg')
/* {
* name: "local-pkg",
* version: "0.1.0",local-pkg vs the alternatives
Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.
| Package | Weekly downloads | Dependents | License | Last release |
|---|---|---|---|---|
| local-pkgthis page | 0 | 5 | MIT | 3 months ago |
| find-up | 0 | 4 | MIT | 1 day ago |
| pkg-dirdeprecated | 0 | 1 | MIT | 1 day ago |
| find-up-simple | 0 | 2 | MIT | 1 day ago |
| test-exclude | 0 | 1 | ISC | 1 day ago |
| validate-npm-package-name | 0 | 1 | ISC | 1 day ago |
Dependencies
Declared by local-pkg v1.2.1. Runtime dependencies are installed with the package; dev dependencies are not.
Runtime (3)
Dev (14)
Used by
Popular packages that depend on local-pkg.
Next generation testing framework powered by Vite
Vite DevTools
Vite DevTools Kit
DevTools for Vitest
DevTools for the Oxc toolchain
Relationship graph
Dependencies (left) and dependents (right) of local-pkg.
Frequently installed together
Native-ESM powered web dev build tool
Framework for building one portable devtool integration that runs in any viewer.
Structured diagnostic code library
Vite DevTools Kit
Universal filesystem path utils
Unified Package Manager for Node.js
The progressive JavaScript framework for building modern web UI.
Simple yet powerful framework for building command-line apps.
Hub layer that orchestrates devframe docks, terminals, messages, and commands on any host.
DevTools for Rolldown
DevTools for Vite (work in progress)
DevTools for Vitest
Release history
6 releases in the last two years, typically about 51 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 1.2.1latest | 3 months ago | 20 KB | MIT |
| 1.2.0 | 3 months ago | 20 KB | MIT |
| 1.1.2 | 1 year ago | 20 KB | MIT |
| 1.1.1 | 1 year ago | 20 KB | MIT |
| 1.1.0 | 1 year ago | 20 KB | MIT |
| 1.0.0 | 1 year ago | 17 KB | MIT |
| 0.5.1 | 1 year ago | 27 KB | MIT |
| 0.5.0 | 2 years ago | 26 KB | MIT |
| 0.4.3 | 3 years ago | 28 KB | MIT |
| 0.4.2 | 4 years ago | 25 KB | MIT |
| 0.4.1 | 4 years ago | 27 KB | MIT |
| 0.4.0 | 4 years ago | 26 KB | MIT |
| 0.3.0 | 5 years ago | 26 KB | MIT |
| 0.2.0 | 5 years ago | 26 KB | MIT |
| 0.1.0 | 5 years ago | 7.3 KB | MIT |
Overview
local-pkg is an npm package that get information on local packages. It has 5 known dependents in the graph. The latest version is 1.2.1, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need get information on local packages and value a focused solution.
When not to use it
Consider an alternative if you need to minimize your dependency tree, or if a more actively-maintained option better fits your npm stack.
Pros
- Ships TypeScript type definitions.
- Clear open-source license (MIT).
Cons
- Large dependency tree (17 direct dependencies) increases install size and audit surface.
Auto-generated from collected registry metadata. No external claims are inferred.
Keywords
Funding
Frequently asked questions
Should I use local-pkg?
Yes — local-pkg scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 112 days ago. 7 releases in the last 2 years.
How do I install local-pkg?
Run `npm install local-pkg` to add local-pkg to your npm project.
How many dependencies does local-pkg have?
local-pkg declares 17 direct dependencies and pulls in 8 packages in total once its runtime tree is resolved totalling about 1.1 MB on disk.
What license is local-pkg released under?
local-pkg is distributed under the MIT license.
How popular is local-pkg?
npm does not publish download counts. Within PackageGraph's crawl, 5 known packages depend on local-pkg.
Is local-pkg still maintained?
The most recent release of local-pkg (v1.2.1) was published 3 months ago.
Does local-pkg run install scripts?
No. local-pkg does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.