Interface ChecksOptions

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.

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.

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.

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

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

See output.cleanDir.

Whether to emit warnings when both the code and postBanner contain shebang

Having multiple shebangs in a file is a syntax error.

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.

Whether to emit warnings when detecting uses of direct evals.

See Avoiding Direct eval in Troubleshooting page for more details.

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

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.

Whether to emit warnings when a module is dynamically imported but also statically imported, making the dynamic import ineffective for code splitting.

Whether to emit warnings when a #__PURE__ / @__PURE__ annotation has no effect due to its position.

Annotations placed where they cannot annotate a call expression (e.g. before a non-call expression, before a statement declaration, or between an identifier and = in a variable declarator) are ignored by the parser. Matches Rollup's INVALID_ANNOTATION log code.

By default, warnings are emitted only for local project files inside cwd and outside node_modules. Set this option to false to disable the warning entirely.

Whether to emit info logs when a barrel module has a very large number of re-exports (more than 5000).

Such modules can significantly slow down module resolution. Consider using @rolldown/plugin-transform-imports to rewrite barrel imports at the source level so the barrel file is never loaded.

See Large barrel modules for more details.

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

See output.globals.

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

See output.name.

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

See output.exports.

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

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.

Whether to emit warnings when a plugin transforms code without generating a sourcemap.

Whether to emit warnings when detecting tolerated transform.

Whether to emit warnings when an entrypoint cannot be resolved.

Whether to emit warnings when an import cannot be resolved.

Whether to emit warnings when a tsconfig option or combination of options is not supported.