node-resolve-pkg 0.2.0-1 source package in Ubuntu

Changelog

node-resolve-pkg (0.2.0-1) unstable; urgency=low

  * Initial release (Closes: #847362)

 -- Sruthi Chandran <email address hidden>  Wed, 07 Dec 2016 20:07:52 +0530

Upload details

Uploaded by:
Debian Javascript Maintainers on 2016-12-08
Uploaded to:
Sid
Original maintainer:
Debian Javascript Maintainers
Architectures:
all
Section:
misc
Urgency:
Low Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Groovy release on 2020-04-24 universe misc
Focal release on 2019-10-18 universe misc
Eoan release on 2019-04-18 universe misc
Bionic release on 2017-10-24 universe misc

Builds

Zesty: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
node-resolve-pkg_0.2.0-1.dsc 2.0 KiB 37b527839d4461136794ed3ebffdfcf0971bca036cef706f2ef56a081d62c916
node-resolve-pkg_0.2.0.orig.tar.gz 2.8 KiB b4dae4b5d71627c9fe6145546168eee3ef2d843b40412520e651d1d53343ac5b
node-resolve-pkg_0.2.0-1.debian.tar.xz 2.1 KiB a5419e9707533dc9feafd4df7e7e2aed7f407f9deaea3de1199f142b2df83066

No changes file available.

Binary packages built by this source

node-resolve-pkg: Resolve the path of a package regardless of it having an entry point

 Some packages like CLI tools and grunt tasks don't have a entry point, like
 `"main": "foo.js"` in package.json, resulting in them not being resolvable by
 `require.resolve()`. Unlike `require.resolve()`, this module also resolves
 packages without an entry point, returns `null` instead of throwing when the
 module can't be found, and resolves from `process.cwd()` instead `__dirname`
 by default.
 .
 Node.js is an event-based server-side JavaScript engine.