The `node-modules` package provides both a command-line interface (CLI) tool and a Node.js module for searching `node-modules.com`. Its primary functionality involves querying the site for packages, with an option to personalize results based on GitHub follows or stars. The current stable version is 1.0.1. Given its age and reliance on `node-modules.com` (which is no longer a primary source for package discovery, superseded by npmjs.com), the package has likely ceased active development. It does not appear to follow a regular release cadence and is designed for an ecosystem context that has largely evolved, making its key differentiator (integration with `node-modules.com`) less relevant today.
npm install node-modulesVerified import paths — ran on the pinned version, not inferred.
Demonstrates how to use the `node-modules` library to perform a search and process the streamed results, including basic error handling.
There is no direct fix for the unavailability of the backend service. Users should consider alternative package search tools like `npm search` or directly browsing `npmjs.com`.
For use in CJS environments, use `const search = require('node-modules');`. In ESM environments, a dynamic `import()` or a CJS wrapper might be necessary: `const search = await import('node-modules').then(m => m.default || m);` (though `m.default` is unlikely for this package, it's good practice for others).Due to its abandoned status, it's recommended to avoid using this package for new projects. For existing projects, perform a security audit of its dependencies (e.g., `npm audit`) and consider migrating to actively maintained alternatives.
Install the package globally using `npm install -g node-modules`.
Use `const search = await import('node-modules');` or convert your file to CommonJS. However, given the package's design, using it in modern ESM projects is generally discouraged.This issue is inherent to the dependency on a potentially defunct external service. There is no code-level fix for this specific package. You must use alternative package discovery methods.
No dependency data recorded yet.