Module to hook into the Node.js require function
JavaScript · active 2025-01-30 → 2026-03-19 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 414 days from 2025-01-30 to 2026-03-19. Pushes: 11 total, peak 3 in a day. Pull requests: 19 total, peak 6 in a day. Issues: 14 total, peak 2 in a day. Comments: 43 total, peak 7 in a day. Stars: 6 total, peak 1 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| timfish | 53 | 9 | 11 | 16 |
| trentm | 14 | 0 | 1 | 6 |
| haines | 9 | 0 | 1 | 6 |
| jsumners-nr | 8 | 0 | 0 | 0 |
| nodejs-github-bot | 7 | 2 | 2 | 3 |
| watson | 5 | 0 | 2 | 1 |
| BYK | 4 | 0 | 1 | 3 |
| pilaoda | 4 | 0 | 0 | 3 |
| Netail | 2 | 0 | 0 | 2 |
| wpessers | 2 | 0 | 1 | 0 |
| douglasg14b | 2 | 0 | 0 | 1 |
| AbhiPrasad | 2 | 0 | 0 | 0 |
| anotheri | 1 | 0 | 0 | 1 |
| dargmuesli | 1 | 0 | 0 | 0 |
| legendecas | 1 | 0 | 0 | 1 |
Recent activity
Latest issues, pull requests and releases
- Pull request#121wpessers2026-03-19 23:16
- Issue comment#120trentm2025-12-03 17:57Removal of resolve module fallback in v8.0.0 can cause resolution issues in (webpack) bundled code
- Issue#120wpessers2025-11-27 23:30Removal of resolve module fallback in v8.0.0 can cause resolution issues in (webpack) bundled code
- Issue comment#115Netail2025-10-22 11:56webpack warning since 7.5.0
- Issue comment#115trentm2025-10-22 02:43webpack warning since 7.5.0
- Issue comment#115Netail2025-10-21 18:05webpack warning since 7.5.0
- Issue comment#119nodejs-github-bot2025-10-20 12:27chore: release v8.0.1
- Releasenodejs-github-bot2025-10-20 12:26require-in-the-middle: v8.0.1
- Issue comment#114pilaoda2025-10-17 13:10Performance degradation when use with tsconfig-paths after require-in-the-middle@7.5.0
- Issue comment#114timfish2025-10-17 12:46Performance degradation when use with tsconfig-paths after require-in-the-middle@7.5.0
- Issue#115timfish2025-10-17 08:35webpack warning since 7.5.0
- Pull request#118timfish2025-10-16 17:10
- Issue#71timfish2025-10-16 17:03use `resolve` just for resolve-y things, use `is-core-module` for "is this a core module" things
- Releasenodejs-github-bot2025-09-24 14:19require-in-the-middle: v8.0.0
- Pull request#116timfish2025-09-24 14:19
- Issue comment#104BYK2025-09-24 13:09feat!: Remove dependency on `resolve` module
- Issue comment#104timfish2025-09-24 12:55feat!: Remove dependency on `resolve` module
- Issue comment#115timfish2025-09-23 15:03`require function is used in a way in which dependencies cannot be statically extracted` since 7.5.0
- Issue comment#115timfish2025-09-23 14:43`require function is used in a way in which dependencies cannot be statically extracted`
- Issue comment#104timfish2025-06-17 00:00feat!: Remove `resolve` dependency which increases min Node version to v8.10.0
- Issue comment#104anotheri2025-06-06 13:00feat!: Remove `resolve` dependency which increases min Node version to v8.10.0
- Issue comment#114pilaoda2025-03-21 05:23Performance degradation when use with tsconfig-paths after require-in-the-middle@7.5.0
- Issue comment#114pilaoda2025-03-16 16:42Performance degradation when use with tsconfig-paths after require-in-the-middle@7.5.0
- Issue comment#114timfish2025-03-16 15:27Performance degradation when use with tsconfig-paths after require-in-the-middle@7.5.0
- Issue#114pilaoda2025-03-15 19:43Performance degradation when use with tsconfig-paths after require-in-the-middle@7.5.0
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 6 stars here means stars gained during the window, not the repo's star count.