Future of svemix

[pixelmund]

Describe the bug

The new routing changes in kit will probably change the future of svemix.

I've just managed to avoid generating the page endpoints in #54 and i'm a little bit frustrated now because the new routing proposal would make svemix kinda obsolete. I love svemix because you can write your server code directly inside your svelte files.

I see a few ways to continue svemix

• Fork SvelteKit before the new routing changes and try to be up to date with any changes in kit unrelated to routing.
• Change svemix to use the new folder-based routing.
• Discontinue svemix

Your Example Website or App

Steps to Reproduce the Bug or Issue

Expected behavior

Screenshots or Videos

Platform

Additional context

No response

[trasherdk]

You are not alone in feeling frustrated. The change will obsolete most youtube tutorials, a shitload of github repositories.
I will discontinue my experiments, until that thing has settled.

[yousufiqbal]

I've an advice that may sound funny. But I think this sort of project should be based upon svelte not sveltekit. Also the current routing changes in sveltekit has created a room for a sveltekit competitor framework. I love SvelteKit but many including me would also welcome a new SvelteKit alternative. Just think about it.