Bring your netlify.toml redirects and headers when you move to Evolving Edge

AddedCLI0.5.1

TL;DR: The new ee-migrate command translates the redirects and headers in a Netlify site's netlify.toml into the _redirects and _headers files Evolving Edge serves. It reports every setting it carried over, changed or left out, with the line it came from.

A Netlify site usually keeps most of its redirects and headers in netlify.toml, which Evolving Edge doesn’t read. Now the ee-migrate command translates its [[redirects]] and [[headers]] into the _redirects and _headers files Evolving Edge serves, so you don’t have to rewrite them by hand.

How to run it

npx --package=@evolving-edge/ee-cdn-cli ee-migrate ./my-site

Leave out the folder to use the current one.

  • --strict makes the command fail when a setting was left out.
  • --report, --redirects and --headers choose where the report and the two files are written.
  • It gets ee-builder the same way ee-deploy does. It downloads and checks it, and runs it without your deploy token.
  • It needs the ee-builder published on 10 November 2026 or later. If your site pins an older one, it stops, tells you how to get a newer one, and leaves .ee-builder-lock.json as it was.
  • Exit status: 0 when the files and report are written, even if some settings were left out. With --strict, 1 when something was left out.

“Moving from Netlify” in the ee-cdn-cli README has more detail.

What it does

  • It reports every setting. You see what was carried over, what was changed and what was left out, each with the line in netlify.toml it came from and the reason. The same report is saved as ee-migrate-report.json.
  • What it writes deploys. Every rule it writes passes the same checks a deploy runs.
  • Your own files come first. If your site already has _redirects or _headers, they stay where they are, with their rules first, as on Netlify. The translated rules follow in a marked block, and running it again replaces only that block.
  • Rules it can’t carry over stay in the file as comments, and are tried again each time you run it, so they come back once Evolving Edge supports them.
  • pretty_urls = true turns on clean URLs, unless your file already sets them.
  • Build settings and [dev] are listed as handled elsewhere, not as left out. --strict fails only when something was actually left out.
  • Your build environment variables stay private. Their names and values are never printed or written.

Limits

  • Functions, edge functions, plugins and proxies aren’t carried over. They’re listed in the report.
  • A domain-level redirect that follows a catch-all is reported as changed, because here domain rules apply first.

What you need to do

Nothing, unless you’re moving a site from Netlify. If you are, run ee-migrate on the site’s folder before you deploy it.

← All changes · More CLI changes · Subscribe to CLI

View as Markdown