You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As mentioned in #2369 (comment), config.kit.prerender.entries (alongside crawl: false) is the solution to this problem. You can put something like this in your svelte.config.js...
npm run build -- /an-article-i-want-to-update /another-article-i-want-to-update
to update /an-article-i-want-to-update and /another-article-i-want-to-update. Or, if you have some programmatic way of determining which URLs have changed, you can put that logic in your config file instead. We could add a new argument to svelte-kit build, but it would only be marginally more convenient than what's already possible in userland, and it wouldn't help in the programmatic case.
Of course, if you're using a hosted CI service then you need to be able to access the previously built pages somehow — there's nothing SvelteKit can do to help with that.
A better solution to all this would be to have some form of incremental static regeneration (#661), but that's a post-1.0 TODO.
The text was updated successfully, but these errors were encountered:
this is the way...
sveltejs/kit#2369 (comment)
The text was updated successfully, but these errors were encountered: