checks
- Type: object with the properties below
- Optional
Controls which warnings are emitted during the build process. Each option can be set to true (emit warning) or false (suppress warning).
cannotCallNamespace?
- Type:
boolean - Optional
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
truecircularDependency?
- Type:
boolean - Optional
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
falsecommonJsVariableInEsm?
- Type:
boolean - Optional
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
trueconfigurationFieldConflict?
- Type:
boolean - Optional
Whether to emit warnings when a config value is overridden by another config value with a higher priority
Default
truecouldNotCleanDirectory?
- Type:
boolean - Optional
Whether to emit warnings when Rolldown could not clean the output directory
See output.cleanDir.
Default
trueemptyImportMeta?
- Type:
boolean - Optional
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
trueeval?
- Type:
boolean - Optional
Whether to emit warnings when detecting uses of direct evals
See Avoiding Direct eval in Troubleshooting page for more details.
Default
truefilenameConflict?
- Type:
boolean - Optional
Whether to emit warnings when files generated have the same name with different contents
Default
trueimportIsUndefined?
- Type:
boolean - Optional
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
truemissingGlobalName?
- Type:
boolean - Optional
Whether to emit warnings when the output.globals option is missing when needed
See output.globals.
Default
truemissingNameOptionForIifeExport?
- Type:
boolean - Optional
Whether to emit warnings when the output.name option is missing when needed
See output.name.
Default
truemixedExports?
- Type:
boolean - Optional
Whether to emit warnings when the way to export values is ambiguous
See output.exports.
Default
truepluginTimings?
- Type:
boolean - Optional
Whether to emit warnings when plugins take significant time during the build process
When enabled, Rolldown measures time spent in each plugin hook. If plugins significantly impact build performance, a warning is emitted with a breakdown of plugin timings.
How it works:
Minimum build time: To avoid noisy warnings for fast builds, the warning is only triggered if Rolldown's internal build time (Rust side) exceeds 3 seconds.
Detection threshold: A warning is triggered when plugin time (total build time minus link stage time) exceeds 100x the link stage time. This threshold was determined by studying plugin impact on real-world projects.
Identifying plugins: When the threshold is exceeded, Rolldown reports up to 5 plugins that take longer than the average plugin time, sorted by duration. Each plugin shows its percentage of total plugin time. Only plugins with total duration of at least 1 second are included in the report.
WARNING
For hooks using ctx.resolve() or ctx.load(), the reported time includes waiting for other plugins, which may overestimate that plugin's actual cost.
Additionally, since plugin hooks execute concurrently, the statistics represent accumulated time rather than wall-clock time. The measured duration also includes Rust-side processing overhead, Tokio async scheduling overhead, NAPI data conversion overhead, and JavaScript event loop overhead.
Default
truepreferBuiltinFeature?
- Type:
boolean - Optional
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
truetoleratedTransform?
- Type:
boolean - Optional
Whether to emit warnings when detecting tolerated transform
Default
trueunresolvedEntry?
- Type:
boolean - Optional
Whether to emit warnings when an entrypoint cannot be resolved
Default
trueunresolvedImport?
- Type:
boolean - Optional
Whether to emit warnings when an import cannot be resolved
Default
true