Is Rollup down? User reports show no current problems with Rollup

Is Rollup Down Right Now?

No, Rollup is not down in the hosted sense. Rollup is a module bundler that runs on your own machine during a build. The reports above show the current Rollup status from developers hitting build errors.

When many developers report the same failure, a new release or a plugin update is often the cause. A Rollup outage in your pipeline usually traces to config, plugins, or a version mismatch. This page tracks Rollup down reports and the fixes that work. The apps they build include customer portals, and a refused login on Romande Energie draws the same pile of morning reports.

Is Rollup Down for Me or Everyone?

Build the smallest test file with your config to split causes. If the tiny build passes, one of your imports or plugins breaks the full build. If it fails too, the config itself needs work.

Check what changed since the last green build. A plugin bump or a new dependency version explains most sudden failures. Rollback the newest change first and rebuild before deeper surgery.

Why Does Rollup Say a Module Is Not Exported?

This error appears when you import a named value that the target file does not export. It is very common with CommonJS packages that Rollup cannot read statically. The message names both files, which speeds the fix.

The CommonJS plugin has named export settings for stubborn packages. Add the package there only when the import is real. If the export truly does not exist, the import in your code is simply wrong.

Why Does Rollup Warn About Unresolved Dependencies?

Rollup treats imports it cannot find as external by default. Bare imports from node modules trigger this warning without the node resolve plugin. The bundle then expects the package to exist at runtime.

Add the resolve plugin before the CommonJS plugin in your config. Order matters for mixed module formats. If the import should stay external, list it under external to silence the warning cleanly.

Why Did the Build Break After a Plugin Update?

Plugins and Rollup move on separate release tracks. A new plugin may need a newer Rollup core, or the reverse. The error stack usually points at the plugin that failed to load.

Read the plugin changelog for peer version notes. Align the versions in your package file and reinstall from scratch. Keeping a lock file stops surprise upgrades inside team builds and CI.

Common Rollup Problems and Fixes

Error says a value is not exported

Error says a value is not exported: Confirm the target module really exports that name. For CommonJS packages, set named exports in the plugin options. Check your import path for a typo or a wrong file first.

Unresolved dependency warnings

Unresolved dependency warnings: Install the node resolve plugin and place it before the CommonJS plugin. Or mark the package as external if the runtime provides it. Rebuild and confirm the warning list shrinks.

this is undefined error in the bundle

this is undefined error in the bundle: Some libraries assume a different module context than Rollup sets. The CommonJS plugin context options can fix known packages. Test the bundle in a browser after each change to confirm behavior.

CSS files are ignored in the build

CSS files are ignored in the build: Rollup does not process plain CSS imports by itself. Add a CSS plugin that matches your setup. Check the plugin order, since style handling must run before output is written.

Bundle size suddenly grew

Bundle size suddenly grew: A new import may have pulled in a whole library. Import named parts instead of the full package. Turn on a visual report to see which module grew. Tree shaking needs ES module builds.