Question regarding adapters and hydration

[Shinsina]

Do forgive me if this is already accounted for/documented elsewhere or explained in another discussion I hadn't noticed any other discussions relating to this as this may be have been a potentially recent change that impacted older scaffolds of SvelteKit.

Recently updated a project from 1.0.0-next.459 to 1.0.0-next.539 and noticed potentially odd behavior regarding adapters (or rather the lack there of) at some point among the development changes the CLI generated scaffolding via create-svelte now includes @sveltejs/adapter-auto as apart of svelte.config.js via config.kit.adapter.

From my recollection (having started with 1.0.0-next.131) this wasn't always the case and to my knowledge this isn't required/highly advised in order to work with SvelteKit in a development instance, where I have been working with this project exclusively (unlike how it has been the case to install an adapter for production environments). This alongside changes to configuration regarding hydration (as my update also required/requested I remove config.kit.browser.hydrate from svelte.config.js), was namely curious about the following issue.

I managed to "solve" this by adding in the config.kit.adapter configuration option using @sveltejs/adapter-auto and was able to continue working on and operating within my project as normal.

Is this expected behavior? Or is there another means by which options.hydrate is to be accounted for, the error message mentions hydratable as a component prop during compilation but I wasn't necessarily sure how/where I needed to do that or necessarily if it would solve my issue.

Obviously given Kit's already noted "expect breaking changes" prior to version 1.0 "tagline", these sort of changes don't surprise me I simply wished to provide potential discussion or help for others who may have faced a similar issue and weren't able to sort out a fix themselves.