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
Svelte
Posts with mentions or reviews of Svelte.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-05-02.
-
My opinion about opinionated Prettier: 👎
the technical decision how Svelte should treat self-closing html elements was hindered by Prettier:
-
Composable architecture example: Go headless (best practices)
Svelte
-
How to optimise React Apps?
React has introduced measures like batching state updates, background concurrent rendering and memoization to tackle this. My opinion is that the best way to solve the problem is by improving their reactivity model. The app needs to be able to track the code that should be re-run on updating a given state variable and specifically update the UI corresponding to this update. Tools like solid.js and svelte work in this manner. It also eliminates the need for a virtual DOM and diffing.
-
Episode 24/13: Native Signals, Details on Angular/Wiz, Alan Agius on the Angular CLI
Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and more…
- Rich Harris: Svelte parses HTML all wrong
- Mario meets Pareto: multi-objective optimization of Mario Kart builds
- Svelte parses HTML all wrong
-
Svelte for Beginners: Easy Guide
Svelte is a powerful web framework that offers a fresh approach to building web applications. Its simplicity, reactivity model, and built-in features make it an excellent choice for developers looking to create efficient and maintainable applications. By following this guide, you should now have a good understanding of how to get started with Svelte and build your first components, routes, and transitions. You can read more about svelte on the official Svelte website.
-
Trying to use dotnet watch with Svelte
Use .NET features (especially dotnet watch) as a setup for a client-side Svelte application, starting from a simple C# console app.