Skip to content

Interface: ChecksOptions

Properties

cannotCallNamespace?

  • Type: optional cannotCallNamespace: boolean

Whether to emit warnings when a namespace is called as a function

A module namespace object is an object and not a function. Calling it as a function will cause a runtime error.

Default

ts
true

circularDependency?

  • Type: optional circularDependency: boolean

Whether to emit warnings when detecting circular dependency

Circular dependencies lead to a bigger bundle size and sometimes cause execution order issues and are better to avoid.

Default

ts
false

commonJsVariableInEsm?

  • Type: optional commonJsVariableInEsm: boolean

Whether to emit warnings when a CommonJS variable is used in an ES module

CommonJS variables like module and exports are treated as global variables in ES modules and may not work as expected.

Default

ts
true

configurationFieldConflict?

  • Type: optional configurationFieldConflict: boolean

Whether to emit warnings when a config value is overridden by another config value with a higher priority

Default

ts
true

couldNotCleanDirectory?

  • Type: optional couldNotCleanDirectory: boolean

Whether to emit warnings when Rolldown could not clean the output directory

See output.cleanDir.

Default

ts
true

emptyImportMeta?

  • Type: optional emptyImportMeta: boolean

Whether to emit warnings when import.meta is not supported with the output format and is replaced with an empty object ({})

See import.meta in Non-ESM Output Formats page for more details.

Default

ts
true

eval?

  • Type: optional eval: boolean

Whether to emit warnings when detecting uses of direct evals

See Avoiding Direct eval in Troubleshooting page for more details.

Default

ts
true

filenameConflict?

  • Type: optional filenameConflict: boolean

Whether to emit warnings when files generated have the same name with different contents

Default

ts
true

importIsUndefined?

  • Type: optional importIsUndefined: boolean

Whether to emit warnings when an imported variable is not exported

If the code is importing a variable that is not exported by the imported module, the value will always be undefined. This might be a mistake in the code.

Default

ts
true

missingGlobalName?

  • Type: optional missingGlobalName: boolean

Whether to emit warnings when the output.globals option is missing when needed

See output.globals.

Default

ts
true

missingNameOptionForIifeExport?

  • Type: optional missingNameOptionForIifeExport: boolean

Whether to emit warnings when the output.name option is missing when needed

See output.name.

Default

ts
true

mixedExports?

  • Type: optional mixedExports: boolean

Whether to emit warnings when the way to export values is ambiguous

See output.exports.

Default

ts
true

pluginTimings?

  • Type: optional pluginTimings: boolean

Whether to emit warnings when plugins take significant time during the build process

Default

ts
true

preferBuiltinFeature?

  • Type: optional preferBuiltinFeature: boolean

Whether to emit warnings when a plugin that is covered by a built-in feature is used

Using built-in features is generally more performant than using plugins.

Default

ts
true

unresolvedEntry?

  • Type: optional unresolvedEntry: boolean

Whether to emit warnings when an entrypoint cannot be resolved

Default

ts
true

unresolvedImport?

  • Type: optional unresolvedImport: boolean

Whether to emit warnings when an import cannot be resolved

Default

ts
true

Released under the MIT License.