Svelte Package Manager -- a necessity

[CordSocial]

The thing is, while I wish for Svelte to succeed as React has done, Svelte itself needs to have that same wish for itself.

It's now clear that the Svelte team alone, and Vercel -- cannot make Svelte great.

It's the users, the enthusiasts, its lovers, the smart Svelte Open Source developers, its Community, and philosophy that can make Svelte great.

What I once proposed, is that Svelte should have something like NPM called "Resources", (or whatever fitting name) on the Svelte website.

It will be the Package Manager for all things Svelte.

Flutter has this same thing called "pub.dev" ( https://pub.dev )

That is where all packages that make Flutter and Dart great, are found.

And it is the contribution from people all over the world, who came to love Flutter and Dart.

Google alone, could not make Flutter and Dart great -- and by being liberal through PUB.Dev, Flutter and Dart received contribution from people all over the world, to make Flutter and Dart great.

This is the same thing I've been asking from Svelte, but there's been some arrogance in listening.

A USE CASE
I heard about Flutter Web ( https://flutter.dev/multi-platform/web) -- and thought I could use Flutter for my website.

Then the fully featured Server frameworks like "ServerPod" ( https://serverpod.dev ) -- which is like Laravel in the Flutter world, made me believe that all is good to go ahead -- but suddenly, I discovered the shortfall of Flutter Web.

However, because of the openness of the Flutter and Dart ecosystem, Kilian will soon release Jaspr( https://pub.dev/packages/jaspr ) -- that will now make building a fully SEO server rendered website with State Management in Flutter, now a full possibility.

MOVING ON
Svelte should allow a Package Manager-- so that it can receive contribution from people all over the world to make Svelte great.

And all of these resources from Svelte, should all be found in one place-- the Svelte icon packages, Svelte Carousel package, Svelte Font Packages, Svelte Authentication Packages, Svelte Graph Database Packages, Svelte ORM Packages, Svelte UI Components Packages, and all such things, should now come under one Resource Hub:: so that people can find them easily.

People like Huntabyte went out of their way to fork ShadCN for the benefit of Svelte ( https://www.shadcn-svelte.com ), but we don't see encouragement from the Svelte team in encouraging such Svelte lovers.

Svelte Native is there, somewhat dying 😞

CONCLUSION
If Svelte can be more open, and allow a more Liberal ecosystem through the Package Management system, Svelte will grow faster.

[SrGeneroso]

You mean like those awesome lists?
Lists made by random pleople on reddit?
I mean, there are sites to show sites made with svelte or even the discord channel for showcasing those.
I guess the most official would be the society site
You could build a centralized thing, but there are already sites doing it, maybe consider collaborating with them.
Making svelte have a exclusive hub is not worth in my opinion. Svelte seems to play great with already existing libraries, so you don't need svelte-specific resources and that's great. In the same topic, I wonder if svelte already run smoothly with bun or deno, even jsr (the npm "clon" for deno) as that would show that svelte is really interoperable. I would like to see that more than a exclusive "store" for it.

[gterras]

while I wish for Svelte to succeed as React has done

Pretty sure no one wishes for that.

[david-plugge]

That sounds like a vendor lock in