Locate and bundle third-party dependencies in node_modules. 

Locate and bundle third-party dependencies in node_modules

rich_harris

shellscape

guybedford

lukastaegert

@rollup/plugin-node-resolve

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

Object.defineProperty(exports, '__esModule', { value: true });

var isBuiltinModule = require('is-builtin-module');

var pluginutils = require('@rollup/pluginutils');

const readFile$1 = util.promisify(fs.readFile);

const realpath = util.promisify(fs.realpath);

  return (await fileExists(path)) ? realpath(path) : path;

  const wrapped = async (param, done) => {

const isDirCached = makeCache(async (file) => {

const isFileCached = makeCache(async (file) => {

const readCachedFile = makeCache(readFile$1);

    const { customResolveOptions } = opts;

    if (customResolveOptions.moduleDirectory) {

      // eslint-disable-next-line no-param-reassign

      opts.moduleDirectories = Array.isArray(customResolveOptions.moduleDirectory)

        ? customResolveOptions.moduleDirectory

        : [customResolveOptions.moduleDirectory];

        'node-resolve: The `customResolveOptions.moduleDirectory` option has been deprecated. Use `moduleDirectories`, which must be an array.'

    if (customResolveOptions.preserveSymlinks) {

        'node-resolve: `customResolveOptions.preserveSymlinks` is no longer an option. We now always use the rollup `preserveSymlinks` option.'

// Resolves to the module if found or `null`.

// The first import specificer will first be attempted with the exports algorithm.

// If this is unsuccesful because export maps are not being used, then all of `importSpecifierList`

// The first import specifier will first be attempted with the exports algorithm.

// If this is unsuccessful because export maps are not being used, then all of `importSpecifierList`

// will be tried with the classic resolution algorithm

    const exportMapRes = await resolveWithExportMap({

      importSpecifier: importSpecifierList[0],

    if (exportMapRes) return exportMapRes;

  // package has no imports or exports, use classic node resolve

const versionRegexp = /\^(\d+\.\d+\.\d+)/g;

function validateVersion(actualVersion, peerDependencyVersion) {

  // eslint-disable-next-line no-cond-assign

  while ((foundVersion = versionRegexp.exec(peerDependencyVersion))) {

    const [foundMajor, foundMinor, foundPatch] = foundVersion[1].split('.').map(Number);

      `Insufficient Rollup version: "@rollup/plugin-node-resolve" requires at least rollup@${minMajor}.${minMinor}.${minPatch}.`

  const [major, minor, patch] = actualVersion.split('.').map(Number);

    (major === minMajor && (minor < minMinor || (minor === minMinor && patch < minPatch)))

      `Insufficient rollup version: "@rollup/plugin-node-resolve" requires at least rollup@${minMajor}.${minMinor}.${minPatch} but found rollup@${actualVersion}.`

/* eslint-disable no-param-reassign, no-shadow, no-undefined */

const ES6_BROWSER_EMPTY = '\0node-resolve:empty.js';

  for (const value of Object.values(object)) {

    if (typeof value === 'object' && !Object.isFrozen(value)) {

import path, { dirname, resolve, extname, normalize, sep } from 'path';

import isBuiltinModule from 'is-builtin-module';

import { pathToFileURL, fileURLToPath } from 'url';

import { createFilter } from '@rollup/pluginutils';

const readFile$1 = promisify(fs.readFile);

  "description": "Locate and bundle third-party dependencies in node_modules",

  "author": "Rich Harris <richard.a.harris@gmail.com>",

  "homepage": "https://github.com/rollup/plugins/tree/master/packages/node-resolve/#readme",

  "bugs": "https://github.com/rollup/plugins/issues",

    "ci:coverage": "nyc pnpm test && nyc report --reporter=text-lcov > coverage.lcov",

    "ci:lint": "pnpm build && pnpm lint",

    "ci:lint:commits": "commitlint --from=${CIRCLE_BRANCH} --to=${CIRCLE_SHA1}",

    "prepare": "if [ ! -d 'dist' ]; then pnpm build; fi",

    "release": "pnpm --workspace-root plugin:release --pkg $npm_package_name",

    "test:ts": "tsc types/index.d.ts test/types.ts --noEmit"

    "@babel/plugin-transform-typescript": "^7.10.5",

    "@rollup/plugin-commonjs": "^23.0.0",

  extensions: ['.mjs', '.js', '.json', '.node'];

export interface RollupNodeResolveOptions {

   * Additional conditions of the package.json exports field to match when resolving modules.

   * By default, this plugin looks for the `'default', 'module', 'import']` conditions when resolving imports.

   * When using `@rollup/plugin-commonjs` v16 or higher, this plugin will use the

   * `['default', 'module', 'import']` conditions when resolving require statements.

   * Setting this option will add extra conditions on top of the default conditions.

   * See https://nodejs.org/api/packages.html#packages_conditional_exports for more information.

   * If `true`, instructs the plugin to use the `"browser"` property in `package.json`

   * files to specify alternative files to load for bundling. This is useful when

   * bundling for a browser environment. Alternatively, a value of `'browser'` can be

   * added to the `mainFields` option. If `false`, any `"browser"` properties in

   * package files will be ignored. This option takes precedence over `mainFields`.

   * A list of directory names in which to recursively look for modules.

   * A list of absolute paths to additional locations to search for modules.

   * This is analogous to setting the `NODE_PATH` environment variable for node.

   * An `Array` of modules names, which instructs the plugin to force resolving for the

   * specified modules to the root `node_modules`. Helps to prevent bundling the same

   * package multiple times if package is imported from dependencies.

  dedupe?: string[] | ((importee: string) => boolean);

   * Specifies the extensions of files that the plugin will operate on.

   * @default [ '.mjs', '.js', '.json', '.node' ]

   * Locks the module search within specified path (e.g. chroot). Modules defined

   * outside this path will be marked as external.

   * Specifies the properties to scan within a `package.json`, used to determine the

   * If `true`, inspect resolved files to assert that they are ES2015 modules.

   * If `true`, the plugin will prefer built-in modules (e.g. `fs`, `path`). If `false`,

   * the plugin will look for locally installed modules of the same name.

   * An `Array` which instructs the plugin to limit module resolution to those whose

  resolveOnly?: ReadonlyArray<string | RegExp> | null | ((module: string) => boolean);

   * Specifies the root directory from which to resolve modules. Typically used when

   * resolving entry-point imports, and when resolving deduplicated modules.

		{
		"name": "@rollup/plugin-node-resolve",
		"version": "15.0.1",
		"version": "15.0.2",
		"publishConfig": {
		@@ -67,3 +67,3 @@ "access": "public"
		"deepmerge": "^4.2.2",
		"is-builtin-module": "^3.2.0",
		"is-builtin-module": "^3.2.1",
		"is-module": "^1.0.0",
		@@ -70,0 +70,0 @@ "resolve": "^1.22.1"

		@@ -1,2 +0,2 @@
		import { Plugin } from 'rollup';
		import type { Plugin } from 'rollup';

		@@ -3,0 +3,0 @@ export const DEFAULTS: {

Improved metrics

Dependency changes

		@@ -15,3 +15,3 @@ 'use strict';

		var version = "15.0.1";
		var version = "15.0.2";
		var peerDependencies = {
		@@ -865,4 +865,4 @@ rollup: "^2.78.0\|\|^3.0.0"
		// Resolves to the module if found or `null`.
		// The first import specificer will first be attempted with the exports algorithm.
		// If this is unsuccesful because export maps are not being used, then all of `importSpecifierList`
		// The first import specifier will first be attempted with the exports algorithm.
		// If this is unsuccessful because export maps are not being used, then all of `importSpecifierList`
		// will be tried with the classic resolution algorithm
		@@ -869,0 +869,0 @@ async function resolveImportSpecifiers({

		@@ -11,3 +11,3 @@ import path, { dirname, resolve, extname, normalize, sep } from 'path';

		var version = "15.0.1";
		var version = "15.0.2";
		var peerDependencies = {
		@@ -861,4 +861,4 @@ rollup: "^2.78.0\|\|^3.0.0"
		// Resolves to the module if found or `null`.
		// The first import specificer will first be attempted with the exports algorithm.
		// If this is unsuccesful because export maps are not being used, then all of `importSpecifierList`
		// The first import specifier will first be attempted with the exports algorithm.
		// If this is unsuccessful because export maps are not being used, then all of `importSpecifierList`
		// will be tried with the classic resolution algorithm
		@@ -865,0 +865,0 @@ async function resolveImportSpecifiers({