Svelte: Svelte as a single unified project/framework

[ansarizafar]

If its possible, why don't we merge Svelte and Sapper as a single project/framework with unified Cli, IDE (Svelte studio) and documentation.

Cli / IDE can have a "New" command to generate boilerplate code/template for creating a Component or an App project with a single configuration file (svelte.config.js).

A "Build" Cli / IDE command can compile a Component project into a Svelte/Web component or an App project into a SSR/SSR+PWA, SPA/SPA+PWA, Mixed(SPA+Static) or a Static website based on the selected option.

I think, It would be easier for new developers to adopt Svelte as a single unified project/framework.

[fjorgemota]

Oh, no.

That would mean that Svelte would not be a nice alternative for react and vue at compile time anymore, which is a nice concept where Svelte really rocks.

Please, maintain the projects separated. One thing is a framework, another totally different is a UI framework. Just my 2 cents here.

[paulocoghi]

Each project serves a specific audience and I agree with what @fjorgemota said.

@ansarizafar , I think that, if Sapper and/or Sapper Studio serve you well, IMHO there is no reason to worry about Svelte itself.

[PaulMaly]

I think Vue has a very nice approach - standalone UI library but with officially supported stuff like router, store, etc.

So, if split Sapper to separated libs integrated with Svelte, and Sapper itself could become something like starter-kit for full-featured Svelte-based apps.

[stalkerg]

Looks like many people to be wrong and not distinguish Sapper and Sapper Studio...

[Kiho]

I don't think it's good idea to make svelte can be hosted only in node.js

[fjorgemota]

I like the idea that @PaulMaly suggested, of using the Vue approach of a standalone UI library with officially supported stuff like router, store and so on.

Personally, I would like a router that support modern browsers (the same as Svelte...) with the guard of the Svelte project (svelte-router or something like that..for example). =)

[kylecordes]

Here's a related thought, perhaps in a different direction: Sapper has some quite interesting ideas in the box, separate from Svelte, and worthy of separate attention. In fact, I wish the ideas from Sapper (around convention-based project layout with routing inferred by the directory structure, for example) would get more traction outside of Sapper/Svelte. The convention approach doesn't solve every problem for every app, but for a broad swath of apps it is probably a better default than what most competing frameworks do.