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.
surveyjs.io
featured
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rfcs
Posts with mentions or reviews of rfcs.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-02-05.
-
Forwarding slots to child components
There's an issue open already and a RFC: https://github.com/sveltejs/svelte/issues/6059 https://github.com/sveltejs/rfcs/pull/64
- anyone have a good document besides "read the source code" for the internals of how Svelte works?
-
Convincing management: React vs Svelte
The RFC ticket is here, so if anyone could provide valid use cases, please do it and push hard to make this happen: https://github.com/sveltejs/rfcs/pull/34
-
Svelte pros and cons!
In the state Svelte is as of this day, there are a few bumps making it harder to implement versatile sets of UI primitives / atomical components. Namely, some of the ones I've met are: lack of syntax to cleanly forward directives and transitions to a component's template (https://github.com/sveltejs/rfcs/pull/60), lack of default slot assignment (i.e. automatically assigning a child component to a parent's slot without requiring devs to manually specify slot="..."), inconsistent bind:group behavior when used on components with nested inputs or through a store passed with setContext, etc. I don't have as much experience trying to implement such UI library components with other frameworks I've used (Vue, Angular) so I can't really say for sure that these challenges are confined to Svelte.
-
Some assorted Svelte demos: conditional wrappers, page transitions, actions
Good stuff. The conditional wrapper unfortunately doesn't work with directives, but the forward directive RFC would address that.
-
My Initial Svelte Notes
(Also a con): It's funny to me that a lot of people try to change Svelte to be "light-React" (see the Svelte RFCs). This also tells a lot about React too, it shows what React nails right on the head and what it misses horribly where Svelte got it right.
-
Typescript: keeping generic types across components
It's part of this proposal: https://github.com/sveltejs/rfcs/pull/38
-
How to use Svelte's style directive
Exclusive to elements: Like most Svelte directives (with the exception of on:), this does not work on components. There is an open RFC to allow forwarding directives to components, which would include style directives. However, this RFC has not been accepted at time of writing.
-
How to expose CSS values without bloating up components?
since v3.38.0 https://github.com/sveltejs/rfcs/pull/13 it not yet documented
-
Full-time React developer feeling like a caveman after using Svelte
All of these issues are very valid. For forwarding, I highly suggest you take a look at this RFC I wrote which will make this much https://github.com/sveltejs/rfcs/pull/60
routify
Posts with mentions or reviews of routify.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-07-11.
-
How's routing done in Vanilla Svelte?
Been using Routify in all my projects since I started with Svelte like 3-4 years ago.
-
SvelteKit: How do you handle largish projects with so many +page & +page.server files?
Anyway, it seems you have a problem with Sveltekit routing. You can still use Svelte with other SSR frameworks, such as Astro, a router like https://routify.dev, or switch to another framework altogether.
-
Svelte and abandonware?
Routify is still active and new version in the works. Version 3 can be used https://github.com/roxiness/routify/tree/next
-
Tauri with Svelte or SvelteKit?
I would have to say Svelte with a router like https://routify.dev . My recent blog post originally used sveltekit but I swapped it out last minute
-
Is there a way to restrict access to certain routes using svelte-spa-router
Consider https://github.com/roxiness/routify
-
If anyone can help me with my noob questions
Regarding some suggestions on here recommending SvelteKit: Learning SvelteKit might be a big ask depending on what you're trying to do. If you just want to stick with svelte only for now, and you want to add SPA routing capabilities, consider checking out https://routify.dev there's a ton of documentation for it and it's fairly simple to pick up. ✌🏼
-
State of the Sveltejs Ecosystem?
Routing: We have a few third party ones such as routify, svelte-spa-router and svelte-routing as well as the clientside routers included in SvelteKit and Sapper.
-
Sveltekit - to use or not to use?
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.
-
Learning to cook at home with Parsnip - built entirely with Svelte!
We chose Routify for client-side routing because this was around the time that Sapper seemed like it was being sunset in favor of Sveltekit which doesn't seem production-ready quite yet. We also have plans to statically pre-render the app so it can more-or-less work entirely offline and Routify makes that relatively straightforward (but see below).
-
Comparing Svelte and React
Since svelte does a lot of compile time stuff, I would like to mention Routify, which is compile time SPA routing. For me it worked awesome to accomplish projects with many routes and the need for hash based routing.
See https://routify.dev/ and https://routify.dev/guide/installation/install-to-existing-p...