Security News
NIST Misses 2024 Deadline to Clear NVD Backlog
NIST has failed to meet its self-imposed deadline of clearing the NVD's backlog by the end of the fiscal year. Meanwhile, CVE's awaiting analysis have increased by 33% since June.
@lerna/package-graph
Advanced tools
@lerna/package-graph is a utility for managing and analyzing the dependency graph of packages within a monorepo. It helps in understanding the relationships between different packages and can be used to perform operations like finding dependencies, dependents, and traversing the graph.
Creating a Package Graph
This feature allows you to create a graph of packages from an array of package objects. The graph can then be used to analyze the relationships between the packages.
const { PackageGraph } = require('@lerna/package-graph');
const packages = [
{ name: 'package-a', version: '1.0.0', dependencies: { 'package-b': '^1.0.0' } },
{ name: 'package-b', version: '1.0.0', dependencies: {} }
];
const graph = new PackageGraph(packages);
console.log(graph);
Finding Package Dependencies
This feature allows you to find the dependencies of a specific package within the graph. In this example, it retrieves the dependencies of 'package-a'.
const { PackageGraph } = require('@lerna/package-graph');
const packages = [
{ name: 'package-a', version: '1.0.0', dependencies: { 'package-b': '^1.0.0' } },
{ name: 'package-b', version: '1.0.0', dependencies: {} }
];
const graph = new PackageGraph(packages);
const packageA = graph.get('package-a');
console.log(packageA.localDependencies);
Finding Package Dependents
This feature allows you to find the dependents of a specific package within the graph. In this example, it retrieves the dependents of 'package-b'.
const { PackageGraph } = require('@lerna/package-graph');
const packages = [
{ name: 'package-a', version: '1.0.0', dependencies: { 'package-b': '^1.0.0' } },
{ name: 'package-b', version: '1.0.0', dependencies: {} }
];
const graph = new PackageGraph(packages);
const packageB = graph.get('package-b');
console.log(packageB.localDependents);
depgraph is a tool for creating and analyzing dependency graphs. It provides similar functionality to @lerna/package-graph, such as creating graphs and finding dependencies and dependents, but it is more general-purpose and can be used outside of monorepos.
madge is a JavaScript library that can create dependency graphs for JavaScript and TypeScript projects. It offers visualization features and can detect circular dependencies, which makes it a more feature-rich alternative for visualizing dependencies compared to @lerna/package-graph.
dependency-cruiser is a tool to analyze and visualize dependencies in JavaScript and TypeScript projects. It offers extensive configuration options and can be used to enforce dependency rules, making it a more comprehensive tool for dependency management compared to @lerna/package-graph.
@lerna/package-graph
Lerna's internal representation of a package graph
You probably shouldn't, at least directly.
Install lerna for access to the lerna
CLI.
3.0.0 (2018-08-10)
npm pack
experience (627cfc2)npm pack
before npm publish
(8d80b2c)lerna version
from of lerna publish
(#1522) (8b97394), closes #277 #936 #956 #961 #1056 #1118 #1385 #1483 #1494changed: The package names emitted to stdout are no longer prefixed by a "- ", and private packages are no longer displayed by default.
list: The default output of lerna ls
no longer shows version strings or private packages.
The new alias lerna la
resembles the old output, with the addition of relative path to the package
The new alias lerna ll
is a shortcut for the new --long
option
A new --parseable
option has been added to aid magical piping incantations
--preid
now defaults to "alpha" during prereleases:The previous default for this option was undefined, which led to an awkward "1.0.1-0" result when passed to semver.inc()
.
The new default "alpha" yields a much more useful "1.0.1-alpha.0" result. Any previous prerelease ID will be preserved, just as it was before.
--no-verify
is no longer passed to git commit
by default, but controlled by the new --commit-hooks
option:
The previous behavior was too overzealous, and the new option operates exactly like the corresponding npm version option of the same name.
As long as your pre-commit hooks are properly scoped to ignore changes in package.json files, this change should not affect you. If that is not the case, you may pass --no-commit-hooks
to restore the previous behavior.
<a name="3.0.0-rc.0"></a>
FAQs
Lerna's internal representation of a package graph
The npm package @lerna/package-graph receives a total of 430,118 weekly downloads. As such, @lerna/package-graph popularity was classified as popular.
We found that @lerna/package-graph demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
NIST has failed to meet its self-imposed deadline of clearing the NVD's backlog by the end of the fiscal year. Meanwhile, CVE's awaiting analysis have increased by 33% since June.
Security News
Cloudflare has launched a setup wizard allowing users to easily create and manage a security.txt file for vulnerability disclosure on their websites.
Security News
The Socket Research team breaks down a malicious npm package targeting the legitimate DOMPurify library. It uses obfuscated code to hide that it is exfiltrating browser and crypto wallet data.