get-current-package
Advanced tools
Get the package.json of the currently executing bin.
This is meant to be used in combination with tiny-updater or similar, in order to get the name and the version of the currently executing bin very conveniently, without importing a "package.json" and without hard-coding the values yourself.
npm install get-current-package
You should have something like this in your bin app:
import getCurrentPackage from 'get-current-package';
console.log ( getCurrentPackage () );
Then executing the bin would produce this:
> my-bin
< { name: 'my-bin', version: '1.0.0', ... }
Basically it detects which entrypoint file is being executed and retrieves its package.json.
MIT © Fabio Spampinato
FAQs
Get the package.json of the currently executing bin.
The npm package get-current-package receives a total of 12,712 weekly downloads. As such, get-current-package popularity was classified as popular.
We found that get-current-package demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Malicious Go packages are impersonating popular libraries to install hidden loader malware on Linux and macOS, targeting developers with obfuscated payloads.
Security News
Bybit's $1.46B hack by North Korea's Lazarus Group pushes 2025 crypto losses to $1.6B in just two months, already surpassing all of 2024's $1.49B total.
Security News
OpenSSF has published OSPS Baseline, an initiative designed to establish a minimum set of security-related best practices for open source software projects.