Analyze dependencies from entry points and split code for closure-compiler. 

Analyze dependencies from entry points and split code for closure-compiler

chadhikes

closure-calculate-chunks

Error

Ignore

Warn

License

Maintenance

Miscellaneous

Quality

Supply chain risk

Vulnerability

Admins only

Organization members

Dashboard

<upgradeLink>Upgrade</upgradeLink> to access this feature

About

Blog

Socket CLI

Customers

Socket Dependency Search

Docs

Socket for GitHub

Love

Impersonation Mode Active

Update your browser to the latest version for the best experience.

Your web browser is outdated

Use another browser for the best experience.

Your web browser is unsupported

{{count, number}} commits last two months

{{count, number}} critical severity alert

{{count, number}} critical severity alerts

{{count, number}} dependency vulnerability

{{count, number}} dependency vulnerabilities

{{count, number}} development dependencies

{{count, number}} transitive dependencies

{{count, number}} version published last month

{{count, number}} versions published last month

{{count, number}} version published in last two months

{{count, number}} versions published in last two months

{{count, number}} version published last week

{{count, number}} versions published last week

{{count, number}} version published last year

{{count, number}} versions published last year

Socket undergoes annual SOC2 Type II audits. Socket customers can request a copy of the full SOC2 Type II report.

Allows organization owners and admins to access detailed records of actions taken by members of their organization, complete with timestamps.

Prevent compromised packages from infiltrating your supply chain by monitoring for changes in real-time.

Join our Discord community to get help from Socket engineers and other Socket users.

Compare millions of open source packages on socket.dev

Detect malicious code and risky behavior (e.g. network) in your dependencies using "deep package inspection"

All data is encrypted in transit and at rest using industry standard encryption algorithms.

Get a dedicated Socket account manager and access to Socket’s Customer Success team.

Get dedicated support from Socket engineers via email and Slack.

"Shift left" with the Socket Chrome extension and give intervene early, before developers choose risky or low quality dependencies.

Catch developers using risky dependencies and give them a "speed bump" to encourage good behavior

Install the Socket GitHub app to receive real-time dependency scanning and reports with every pull request.

Integrate Socket into your GitHub SCM to prevent risky dependencies from being installed.

Socket scans for vulnerabilities in your dependencies, including CVEs, security advisories, and more.

Socket supports dependencies in many languages, with most popular ecosystems coming in 2024. We've got you covered no matter what languages you use.

Enforce license policies across your organization

Receive a Microsoft Teams message to the channel of your choice anytime Socket runs a new analysis, has a new finding, or a policy has changed.

Get help migrating from Socket's free plan to Socket's paid plans.

Run Socket on-premises or in your own cloud environment.

Query for any dependency (at any version) across your entire organization

Integrate Socket into your CI/CD pipeline to prevent risky dependencies from being deployed to production.

Analyze an entire project to find supply chain risks

Tag projects to organize and filter your projects

Restrict access based on the roles of individual users within an organization.

Receive a Slack message to the channel of your choice anytime Socket runs a new analysis, has a new finding, or a policy has changed.

Socket is SOC2 Type II compliant and undergoes annual audits.

The Socket CLI allows teams to prevent risky dependencies from being installed, and to get dependency insights from the command line.

Socket supports SAML SSO for single sign-on and identity management.

Integrate Socket into your VS Code IDE to prevent risky dependencies from being installed.

Get a POST request anytime Socket runs a new analysis, has a new finding, or a policy has changed.

Socket will analyzed your SBOMs up to a maximum number of dependencies.

API that allows you to analyze a project, lookup package scores and alerts, and more.

Create API tokens to authenticate with the Socket API and CLI.

The number of developers in your team. A developer is someone who made a commit to your organization's repositories scanned by Socket in the past month.

Use Socket to protect your private repositories.

Socket is always free for open source projects.

Socket retains all reporting data for 3 months, 1 year, or a custom term of your choice.

Access the threat feed that powers Socket.

Unlimited scale, self-hosting, and priority support for large teams.

For open-source projects, individuals, and small teams.

For growing teams with enhanced scale, security, and support.

There is a package with a similar name that is downloaded much more often.

There are packages with similar names that are downloaded much more often.

This may not be the package you want!

Instance

Alert Locations

Package

The {{ecosystem}} package {{- packageName}} receives a total of <strong>{{numWeeklyDownloadCount, number}}</strong> weekly downloads. As such, {{- packageName}} popularity was classified as <strong>{{popularity}}</strong>.

Is {{- packageName}} popular?

Is {{- packageName}} safe to use?

Is {{- packageName}} well maintained?

What is {{- packageName}}?

{{packageDescription}}Version: {{versionString}} was published by {{publisherName}}. Start using Socket to analyze {{- packageName}} and its {{dependencyCount, number}} dependencies to secure your app from supply chain attacks.

Sorry, it seems this package was removed from the registry

Package was removed

This package version has been unpublished, mostly likely due to security reasons

Package version was removed

Provide a detailed description of the malware...

Socket fights vulnerabilities and provides visibility, defense-in-depth, and proactive supply chain protection for JavaScript, Python, and Go dependencies.

Socket - Secure your dependencies. Ship with confidence.

Compare versions

{{- packageName}} - npm Package Compare versions

import ChunkGraph from './lib/chunk-graph.js';

import parseGoogDeps from './lib/parse-goog-deps.js';

import generateHtml from './lib/generate-html.js';

import {NAMING_STYLE} from './lib/chunk-naming.js';

function resolveFrom(filepath, moduleId) {

  const requireFrom = Module.createRequire(filepath);

const packageJson = JSON.parse(fs.readFileSync(new URL('./package.json', import.meta.url), 'utf8'));

      describe: 'Format: <path/to/file>. Main entrypoint for the program. The first occurrence will be treated as the primary entrypoint. Additional entrypoints will be added as children of the primary entrypoint. Multiple files may be listed for a single entrypoint, separated by commas, to indicate they are both part of the same chunk.',

      describe: 'Format: <path/to/Parent>:<path/to/Child>. Add an arbitrary chunk entrypoint to the graph. Multiple children may be listed separated by commas.',

      describe: 'Format: <path/to/project/root>. Path to the project root directory. The current working directory of the process is used by default.',

    .option('closure-library-base-js-path', {

      describe: 'Format: <path/to/base.js>. Path to closure-library\'s base.js file. Required if closure-library or goog.module references are used.',

      describe: 'Fomrat: <path/to/deps.js>. Path to closure-library deps.js file or custom deps.js file. Used to find paths to closure-library namespaces.',

      requiresArg: 'closure-library-base-js-path'

      describe: 'Format: <namespace>:<path/to/file>. Namespace and path to a file providing a closure namespace or module.',

      describe: 'Create and open an html page to visualize the graph.',

    .option('package-json-entry-names', {

      describe: 'Ordered list of entries to look for in package.json files when resolving modules',

      describe: 'How the name of a chunk is determined. For "entrypoint", chunk names are derived from the imported ' +

          'file name. For "numbered", the entrypoint is named "main" and child chunks are numeric indexes.',

      choices: Array.from(Object.values(NAMING_STYLE)),

    .coerce('package-json-entry-names', (arg) => arg.split(/,\s*/g))

        const manualEntrypoints = Array.isArray(argv.manualEntrypoint) ? argv.manualEntrypoint : [argv.manualEntrypoint];

        manualEntrypoints.forEach((manualEntrypoint) => {

          const parts = manualEntrypoint.split(':');

            throw new Error('manual-entrypoints must be of the form "<path/to/Parent>:<path/to/Child>"');

        const extraDeps = Array.isArray(argv['extra-deps']) ? argv['extra-deps'] : [argv['extra-deps']];

          const depParts = dep.split(':');

            throw new Error('extra-deps must be of the form "<namespace>:<path/to/file>"');

    .usage('Usage: node $0 --entrypoint src/main.js')

  if (/^[a-z]/.test(option) && !/-/.test(option)) {

const entrypoints = (Array.isArray(flags.entrypoint) ? flags.entrypoint : [flags.entrypoint])

      const entrypointFiles = entrypoint.split(',')

      const namingStyle = flags.namingStyle === NAMING_STYLE.NUMBERED ? NAMING_STYLE.NUMBERED : NAMING_STYLE.ENTRYPOINT;

        generateHtml(chunkGraph, namingStyle)

            .then((html) =>  new Promise((resolve, reject) => {

              const tempFile = temp.path({ prefix: 'closure-calculate-chunks-', suffix: '.html' });

              fs.writeFile(tempFile, html, 'utf8', (err) => {

              console.log("Created temp file", tempFilePath);

              const childProcess = open(tempFilePath);

                // Catch error output from child process

                childProcess.stderr.once('data', (error) => {

                  console.error({ code: 'CannotOpenTempFile', tempFilePath, error });

          process.stdout.write(JSON.stringify(chunkGraph.getClosureCompilerFlags(namingStyle), null, 2) + '\n');

          process.stderr.write(`Error: ${e.message}\n`);

import DepsFinder from './deps-finder.js';

import normalizeGraph from './normalize-graph.js';

import {NAMING_STYLE, outputChunkNaming} from './chunk-naming.js';

 * A graph of output chunks built from an entrypoint. Separate chunks are split off

  /** @type {!Map<string, !Set<string>>} */

  /** @type {!{readFile:(function(string,string):!Promise<string>)}} */

      return fs.readFile(filepath, encoding);

   * @param {!Map<string, !Set<string>>=} sourceReferences

  constructor(entrypoint, graph = new graphlib.Graph({directed: true, compound: false}), sourceReferences = new Map()) {

    this.#sourceReferences = sourceReferences;

   * Convert the chunk load order graph to a dependency graph compatible with closure-compiler.

    this.graph.nodes().forEach((nodeName) => {

      const node = this.graph.node(nodeName);

        sourceNodes.set(source, nodeName);

    const dependencyGraph = new graphlib.Graph({compound: false, directed: true});

    /** @type {!Map<string, !Set<string>>} */

      dependencyGraph.setNode(nodeName, node);

      if (nodeName !== this.entrypoint) {

        // By definition, every node has a dependency on the entrypoint

        const containingChunk = sourceNodes.get(dep);

        if (containingChunk !== nodeName) {

      parentNodes.set(nodeName, parents);

    // Add edges from each node to its parent - but omit parents which are transitively available through

    // Example: If A depends on both B & C, but B also depends on C, only add edge B -> A.

    dependencyGraph.nodes().forEach((nodeName) => {

      const transitiveParents = new Set();

      parentNodes.get(nodeName).forEach((parentNodeName) => {

        parentNodes.get(parentNodeName).forEach((grandparentNodeName) => {

          transitiveParents.add(grandparentNodeName);

        if (!transitiveParents.has(parentNodeName)) {

          dependencyGraph.setEdge(parentNodeName, nodeName);

   * @param {!Array<string>} packageJsonEntryNames prefence order of fields to look for in package.json files for the main file

   * @param {!Array<{name:string, files: !Array<string>}>} entrypoints paths from which to start building the graph.

   *     The first entry is the primary entrypoint.

   * @param {!Array<{parent: string, child: {name: string, files: !Array<string>}}>} manualEntrypoints additional files to be manually added.

   * @param {!Array<string>=} packageJsonEntryNames prefence order of fields to look for in package.json files for the main file

   * @param {string=} baseDirectory root directory of application

   * @param {string=} googBasePath path to closure library base.js

   * @param {!Map<string, string>=} googDepsMap map of closure library provided namespace to filepath

      packageJsonEntryNames = ['browser', 'module', 'main'],

    const depFinder = new DepsFinder(packageJsonEntryNames, baseDirectory, googBasePath, googDepsMap, this.fsAdapter);

    let graphData = await depFinder.fromEntryPoints(entrypoints, manualEntrypoints);

    depFinder.fileDependencies.forEach((node, filename) => {

        let references = sourceReferences.get(dep);

          sourceReferences.set(dep, references);

    let chunkGraph = new this(graphData.entrypoint, graphData.graph, sourceReferences);

    const dependenciesToHoist = normalizeGraph(chunkGraph.entrypoint, chunkGraph.graph);

    dependenciesToHoist.forEach((sources) => {

      depFinder.addDependenciesToHoist(dependenciesToHoist);

		@@ -154,5 +154,5 @@ #!/usr/bin/env node
		.buildFromEntrypoints(
		flags.packageJsonEntryNames,
		entrypoints,
		manualEntrypoints,
		flags.packageJsonEntryNames,
		rootDir,
		@@ -159,0 +159,0 @@ googBasePath,

		{
		"name": "closure-calculate-chunks",
		"version": "3.0.0",
		"version": "3.0.1",
		"description": "Analyze dependencies from entry points and split code for closure-compiler",
		@@ -5,0 +5,0 @@ "bin": {

		@@ -177,6 +177,6 @@ import graphlib from 'graphlib';
		*
		* @param {!Array<string>} packageJsonEntryNames prefence order of fields to look for in package.json files for the main file
		* @param {!Array<{name:string, files: !Array<string>}>} entrypoints paths from which to start building the graph.
		* The first entry is the primary entrypoint.
		* @param {!Array<{parent: string, child: {name: string, files: !Array<string>}}>} manualEntrypoints additional files to be manually added.
		* @param {!Array<string>=} packageJsonEntryNames prefence order of fields to look for in package.json files for the main file
		* @param {string=} baseDirectory root directory of application
		@@ -188,5 +188,5 @@ * @param {string=} googBasePath path to closure library base.js
		static async buildFromEntrypoints(
		packageJsonEntryNames,
		entrypoints,
		manualEntrypoints = [],
		packageJsonEntryNames = ['browser', 'module', 'main'],
		baseDirectory = process.cwd(),
		@@ -193,0 +193,0 @@ googBasePath = process.cwd(),

Improved metrics