Node.js dependency insight
org.openrewrite.nodejs.search.DependencyInsight
Identify the direct and transitive Node.js dependencies used in a project.
Recipe source
GitHub, Issue Tracker, Maven Central
groupId: org.openrewrite.recipe
artifactId: rewrite-nodejs
version: 0.2.1
Options
Type | Name | Description | Example |
---|---|---|---|
| namePattern | Name glob pattern used to match dependencies. |
|
| version | Optional. Match only dependencies with the specified version. Node-style version selectors may be used.All versions are searched by default. |
|
| onlyDirect | Optional. If enabled, transitive dependencies will not be considered. All dependencies are searched by default. |
|
Data Tables (Only available on the Moderne platform)
Dependencies in use
Direct and transitive dependencies in use.
Column Name | Description |
---|---|
Name | The name of the node package. |
Requested version | The requested version. |
Version | The resolved version. |
Usage
This recipe has required configuration parameters. Recipes with required configuration parameters cannot be activated directly. To activate this recipe you must create a new recipe which fills in the required parameters. In your rewrite.yml
create a new recipe with a unique name. For example: com.yourorg.DependencyInsightExample
. Here's how you can define and customize such a recipe within your rewrite.yml:
Now that com.yourorg.DependencyInsightExample
has been defined activate it and take a dependency on org.openrewrite.recipe:rewrite-nodejs:0.2.1 in your build file:
Add the following to your
build.gradle
file:
Run
gradle rewriteRun
to run the recipe.
See how this recipe works across multiple open-source repositories
The community edition of the Moderne platform enables you to easily run recipes across thousands of open-source repositories.
Please contact Moderne for more information about safely running the recipes on your own codebase in a private SaaS.
Last updated