ee-first
npmv1.1.1return the first event in a set of ee/event pairs
Not recommended for new projects
No — ee-first should not be adopted for new projects. Last published 4125 days ago.
- AAdoption: grade A, Excellent.
79.7M downloads per week and 1 known dependents.
- FMaintenance: grade F, Failing.
Last published 4125 days ago.
- AWeight: grade A, Excellent.
Zero runtime dependencies.
- 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 ee-first 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
- No constraint declared
- Module format
- CommonJS only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the ee-first README.
var first = require('ee-first')Dependencies
Declared by ee-first v1.1.1. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (2)
Used by
Popular packages that depend on ee-first.
Relationship graph
Dependencies (left) and dependents (right) of ee-first.
Frequently installed together
Release history
No releases in the last two years, typically about 0 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 1.1.1latest | 11 years ago | — | MIT |
| 1.1.0 | 12 years ago | — | MIT |
| 1.0.5 | 12 years ago | — | MIT |
| 1.0.4 | 12 years ago | — | MIT |
| 1.0.3 | 12 years ago | — | MIT |
| 1.0.2 | 12 years ago | — | MIT |
| 1.0.1 | 12 years ago | — | MIT |
| 1.0.0 | 12 years ago | — | MIT |
Overview
ee-first is an npm package that return the first event in a set of ee/event pairs. It is extremely widely used, with about 79.7M downloads per week and 1 known dependents in the graph. The latest version is 1.1.1, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need return the first event in a set of ee/event pairs and value a battle-tested, widely-adopted 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
- Large, well-established user base (79.7M weekly downloads).
- Clear open-source license (MIT).
- Lean dependency tree (2 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
Frequently asked questions
Should I use ee-first?
No — ee-first should not be adopted for new projects. Last published 4125 days ago.
How do I install ee-first?
Run `npm install ee-first` to add ee-first to your npm project.
What license is ee-first released under?
ee-first is distributed under the MIT license.
How popular is ee-first?
ee-first has approximately 79,688,489 downloads per week and 1 known dependent packages.
Is ee-first still maintained?
The most recent release of ee-first (v1.1.1) was published 11 years ago.
Does ee-first run install scripts?
No. ee-first does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.