define-lazy-prop
npmv3.0.0Define a lazily evaluated property on an object
Not recommended for new projects
No — define-lazy-prop should not be adopted for new projects. Last published 1975 days ago.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- FMaintenance: grade F, Failing.
Last published 1975 days ago.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 4.3 KB installed.
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- 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 define-lazy-prop 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.
Compatibility
- Node.js
- node >=12
- Module format
- ESM only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the define-lazy-prop README.
import defineLazyProperty from 'define-lazy-prop';
const unicorn = {
// …
};
defineLazyProperty(unicorn, 'rainbow', () => expensiveComputation());
app.on('user-action', () => {
doSomething(unicorn.rainbow);
});define-lazy-prop 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 |
|---|---|---|---|---|
| define-lazy-propthis page | 0 | 1 | MIT | 5 years ago |
| merge-descriptors | 113M | 1 | MIT | 1 day ago |
| es-define-property | 131.3M | 4 | MIT | 1 day ago |
| rfdc | 46.8M | 3 | MIT | 1 day ago |
| define-data-property | 0 | 2 | MIT | 1 day ago |
| reusify | 91M | 1 | MIT | 1 day ago |
Dependencies
Declared by define-lazy-prop v3.0.0. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (3)
Used by
Popular packages that depend on define-lazy-prop.
Relationship graph
Dependencies (left) and dependents (right) of define-lazy-prop.
Frequently installed together
Get the default browser
Utilities for working with Windows Subsystem for Linux (WSL)
TypeScript definitions for node
Check if the process is running inside a container (Docker/Podman)
Check if the process is running in an SSH session
Release history
No releases in the last two years, typically about 815 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 3.0.0latest | 5 years ago | 4.3 KB | MIT |
| 2.0.0 | 7 years ago | 4.3 KB | MIT |
| 1.0.0 | 9 years ago | — | MIT |
Overview
define-lazy-prop is an npm package that define a lazily evaluated property on an object. It has 1 known dependents in the graph. The latest version is 3.0.0, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need define a lazily evaluated property on an object and value a focused solution.
When not to use it
Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.
Pros
- Clear open-source license (MIT).
- Lean dependency tree (3 direct dependencies).
Cons
- No bundled TypeScript types (may require a separate @types package).
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Funding
Frequently asked questions
Should I use define-lazy-prop?
No — define-lazy-prop should not be adopted for new projects. Last published 1975 days ago.
How do I install define-lazy-prop?
Run `npm install define-lazy-prop` to add define-lazy-prop to your npm project.
What license is define-lazy-prop released under?
define-lazy-prop is distributed under the MIT license.
How popular is define-lazy-prop?
npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on define-lazy-prop.
Is define-lazy-prop still maintained?
The most recent release of define-lazy-prop (v3.0.0) was published 5 years ago.
Does define-lazy-prop run install scripts?
No. define-lazy-prop does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.