Our great sponsors
-
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
-
I maintain a Svelte Starter Kit and all I had to do between several updates is change the layout file names, simplify the hooks, and convert the config file extensions. If you're learning Svelte in 2021, you shouldn't miss learning it, as it's "the missing CLI" and the svelte team's favoured project structure, to build full-stack server rendered and static sites, with File/Folder based routing, focus on server-less with adapters, API routes, and good baked-in conventions and constructs to support common web app needs. It's a successor to Sapper which served the aforementioned needs, with exception of adapters, which is special/unique(with no officially provided parallels in Next.js/Nuxt ecosystems yet) way to make vendor-agnostic, server-less first deployment concern a seamlessly integrated part of the framework.
if Next.js/Nuxt like needs are not something you're looking for yet, you can definitely go ahead with Svelte's default client-side app approach, with svelte-spa-router or routify for SPAs.
if Next.js/Nuxt like needs are not something you're looking for yet, you can definitely go ahead with Svelte's default client-side app approach, with svelte-spa-router or routify for SPAs.
If you wanna explore few open-source Svelte Kit projects, you can visit awesome-svelte-kit or have look at my project here.
I maintain a Svelte Starter Kit and all I had to do between several updates is change the layout file names, simplify the hooks, and convert the config file extensions. If you're learning Svelte in 2021, you shouldn't miss learning it, as it's "the missing CLI" and the svelte team's favoured project structure, to build full-stack server rendered and static sites, with File/Folder based routing, focus on server-less with adapters, API routes, and good baked-in conventions and constructs to support common web app needs. It's a successor to Sapper which served the aforementioned needs, with exception of adapters, which is special/unique(with no officially provided parallels in Next.js/Nuxt ecosystems yet) way to make vendor-agnostic, server-less first deployment concern a seamlessly integrated part of the framework.
if Next.js/Nuxt like needs are not something you're looking for yet, you can definitely go ahead with Svelte's default client-side app approach, with svelte-spa-router or routify for SPAs.