Are the docs wrong when they say to place this file in static and it will work?
https://kit.svelte.dev/docs/adapter-cloudflare#notes

Are the docs wrong when they say to place this file in static and it will work?

https://kit.svelte.dev/docs/adapter-cloudflare#notes

No, the docs are correct.

@nosovk may I know what your use case is for this? If you are attempting to add redirects for a prerendered page , this should work as expected (I was wrong). Otherwise, SSR routes should use Cloudflare redirect rules / page rules, or implement the redirect logic to the sveltekit app itself.

We have site, which is hosted on Cloudflare pages.
Currently, we need to change URL structure (rename categories, move articles over the categories etc.).
When we move pages we should leave 301 redirects on the previous address, and point it to the new destination. We have nearly a hundred redirects... It's much easier to hold them all in __redirects config, that will serve those redirects without launching workers.

Currently we do something like that:

[...rest]/+page.sever.ts

import { error, redirect } from '@sveltejs/kit';
import type { PageServerLoad } from './$types';

const redirects = {
  '/actions': '/what-we-do',
  '/actions/200-days-into-russias-war-on-ukraine': '/whats-new/200-days-into-russias-war-on-ukraine',
// ...
/// ... 
};

export const load: PageServerLoad = async ({ url }) => {
  if (redirects[url.pathname]) {
    throw redirect(301, redirects[url.pathname]);
  }
  throw error(404, 'Not found');
};

and it actually works when we have our categories renamed, like actions => whats-new

But it's really good idea to manage all those redirects in one place, especially if there is some solution from platform.

We have site, which is hosted on Cloudflare pages. Currently, we need to change URL structure (rename categories, move articles over the categories etc.). When we move pages we should leave 301 redirects on the previous address, and point it to the new destination. We have nearly a hundred redirects... It's much easier to hold them all in __redirects config, that will serve those redirects without launching workers.

Thank you for sharing. You've actually helped correct my understanding about Cloudflare Pages redirects (previously I thought the redirect would bypass the worker, thus fail when arriving at the destination).

I'd love to try my hand at implementing this. Although, one thing to be wary of is the 100 rule limit for _routes.json. A number of those rules would already be used up by assets and prerendered pages, leaving very little to no room left for those redirects if your site is very large.

Should the build warn or fail when the _routes.json rules have been exceeded? Should _redirects take priority over static assets and prerendered pages? (which will still be served by the worker if not listed in _routes.json).

We have nearly a hundred redirects...

I would like to add that you cannot add all of your redirects to _routes.json. _routes.json has a limit of 100 rules. Unless many of those redirects could be handled under wildcards

I think that prerendered pages and static assets should be level 1 citizen in routes, and warning user about that limit o space for redirect reached is Ok.
I actually didn't knew about limit of 100 elements in _routes.json. Limit for _redirects is 500 elements, which makes the wholl situation a bit broken... Adding wildcards is a manual approach, which might be not simple at all for most users.

#9111 allows manually excluding routes.

Should the adapter warn the developer when a _redirects file is found and certain routes aren't excluded?

Or should the adapter try to automatically include the routes found in _redirects?

#9111 allows manually excluding routes.

Should the adapter warn the developer when a _redirects file is found and certain routes aren't excluded?

Or should the adapter try to automatically include the routes found in _redirects?

#9111 adds placeholders that allow automatic generation of exclude rules for things like _app, static files, and pre generated pages. I’m planning on adding another placeholder that would excludes redirects

Here's a workaround in the meantime that reads the _redirects file and excludes the routes.

// svelte.config.js
const redirects = readFileSync('./static/_redirects', 'utf8')
	.split('\n')
	.filter(Boolean)
	.map((line) => {
		const [from] = line.split(' ');
		if (!from) {
			throw new Error(`Invalid _redirects entry: ${line}`);
		}
		return from;
	});

const config = {
	kit: {
		adapter: adapter({
			routes: {
				include: ['/*'],
				exclude: ['<all>', ...redirects]
			}
		}),