The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →
Rfcs Alternatives
Similar projects and alternatives to rfcs
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
svelte-subcomponent-preprocessor
A Svelte preprocessor for writing more than one component per file.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a better rfcs alternative or higher similarity.
rfcs reviews and mentions
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
-
A note from our sponsor - WorkOS
workos.com | 25 Apr 2024
Stats
Basic rfcs repo stats
16
271
0.0
4 months ago
Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com