2 comments — live from bluesky
Consider building a community addon. svelte.dev/docs/cli/sv-...
So you can piggyback on the official CLI
It does look like community add-ons are still experimental, but it's something I'll look into. The current version of the club does piggyback off of the official, it just abstracts away most of their prompts in favor of its own.
A perk of following the Svelte CLI community addon path: it’ll get surfaced through various lists, hence increase the probability of adoption / usage npmx.dev/search?q=key...
Do we already automatically surface community add-ons on the @sveltesociety.dev website @kevinak.se @jyc.dev ?
This is a very good point, increased adoption is a major goal. I'm also not that far into development that it shouldn't be too much to pivot. However this cli also handles scaffolding a Svelte(vite) project as well. In your opinion should that stay as its own cli or switch to a vite plugin?
Yes, the CLI also handles non kit projects.
It is experiential. But only because we're still trying to get more feedback from add-on developers on missing APIs.
Even better it also handles js, jsdocs and ts projects.
Feel free to prouse the official add-on or post an issue if you have any questions at GitHub.com/sveltejs/cli...
Today npm/npmx with the right search param is the way 🚀🎉
Came here to say the same. This is probably a good idea instead of a standalone cli.
SvelteKit + PocketBase is the ultimate lean stack. Reducing boilerplate is how we scale innovation faster. Can't wait to see how you handle the schema sync logic! 🚀