Interface: ResolvedDepsConfig

Defined in: src/features/deps.ts:108

Extends

• Pick<DepsConfig, "neverBundle" | "skipNodeModulesBundle" | "resolveDepSubpath">

Properties

alwaysBundle?

optional alwaysBundle?: NoExternalFn;

Defined in: src/features/deps.ts:112

---

dts

dts: Pick<ResolvedDepsConfig, 'alwaysBundle' | 'neverBundle'>

Defined in: src/features/deps.ts:119

Override dependency bundling options for declaration file generation.

---

neverBundle?

optional neverBundle?:
  | true
  | string | RegExp | (string | RegExp)[] | ExternalOptionFunction;

Defined in: src/features/deps.ts:55

Mark dependencies as external (not bundled). Accepts strings, regular expressions, or Rolldown's ExternalOption.

Set to true to externalize all dependencies: every import that follows npm package naming conventions is marked as external as written, without resolving it. Other non-relative imports (e.g. # subpath imports and path aliases like ~/) are resolved, and kept external only if they resolve into node_modules; otherwise the resolved local file is bundled.

Use alwaysBundle to opt specific imports back into the bundle.

Inherited from

DepsConfig.neverBundle

---

onlyBundle?

optional onlyBundle?: false | (string | RegExp)[];

Defined in: src/features/deps.ts:113

---

onlyImport?

optional onlyImport?: (string | RegExp)[];

Defined in: src/features/deps.ts:114

---

resolveDepSubpath?

optional resolveDepSubpath?: boolean;

Defined in: src/features/deps.ts:100

Resolve dependency subpath imports to their actual package-relative paths when externalizing packages without an exports field.

Default

true

Inherited from

DepsConfig.resolveDepSubpath

---

skipNodeModulesBundle?

optional skipNodeModulesBundle?: boolean;

Defined in: src/features/deps.ts:93

Skip bundling all node_modules dependencies.

Note: This option cannot be used together with alwaysBundle.

Default

false

Deprecated

Use neverBundle: true instead.

Inherited from

DepsConfig.skipNodeModulesBundle