Interface: PluginContextResolveOptions

Defined in: packages/rolldown/src/plugin/plugin-context.ts:152

Properties

attributes?

• Type: Record<string, string>
• Optional

Defined in: packages/rolldown/src/plugin/plugin-context.ts:190

The import attributes of the simulated import, passed to resolveId hooks as attributes. Without experimental.importAttributes, hooks get {}, and only an external result keeps them.

Default

{}

---

custom?

• Type: CustomPluginOptions
• Optional

Defined in: packages/rolldown/src/plugin/plugin-context.ts:180

Plugin-specific options.

See Custom resolver options section for more details.

---

isEntry?

• Type: boolean
• Optional

Defined in: packages/rolldown/src/plugin/plugin-context.ts:164

The value for isEntry passed to resolveId hooks.

Default

false if there's an importer, true otherwise.

---

kind?

• Type: "import-statement" | "dynamic-import" | "require-call" | "import-rule" | "url-token" | "new-url" | "hot-accept"
• Optional

Defined in: packages/rolldown/src/plugin/plugin-context.ts:157

The value for kind passed to resolveId hooks.

---

skipSelf?

• Type: boolean
• Optional

Defined in: packages/rolldown/src/plugin/plugin-context.ts:174

Whether the resolveId hook of the plugin from which this.resolve is called will be skipped when resolving.

When other plugins themselves also call this.resolve in their resolveId hooks with the exact same source and importer while handling the original this.resolve call, then the resolveId hook of the original plugin will be skipped for those calls as well. The rationale here is that the plugin already stated that it "does not know" how to resolve this particular combination of source and importer at this point in time. If you do not want this behavior, set skipSelf to false and implement your own infinite loop prevention mechanism if necessary.

Default

true