felte
unocss
felte | unocss | |
---|---|---|
16 | 56 | |
972 | 15,442 | |
- | 2.9% | |
8.1 | 9.7 | |
3 months ago | 2 days ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
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.
felte
-
Big update for sveltekit-superforms!
How does it compare to Felte?
-
sveltekit-superforms alternatives - felte, sveltejs-forms, svelte-forms-lib, svelte-use-form, and svelte-final-form
7 projects | 6 Mar 2023
-
What libraries do you miss from other frameworks like Vue or React?
Don’t know if it can help, but I discovered this only recently, which was really missing for me with svelte: https://felte.dev/
- Introducing Skeleton - a Svelte UI component library for creating web interfaces using Svelte + Tailwind
- Client side form validation
-
Shadow DOM, Firefox and contenteditable
I’ve been experimenting with web components in order to build a wrapper for Felte that can easily be used with vanilla JS. One of Felte’s features is the ability to use custom field components that are not based on the browser’s native inputs (input, textarea, select). The example I show is a div with an attribute [contenteditable=“true”]. While testing this experiment I found some weird behaviour coming from Firefox: while I could perfectly click each field and type of it, if I tried to use the form only using the keyboard (tabbing to each field) the focus moved but trying to type would always result in the text being added to the first field I focused.
-
The use:__ feature giving my editor TS errors, but it works
There’s an example on Felte’s repo setting this up!
-
Using native form with web components + felte no data being passed
Ah. Of course 😅. mwc-textfield is not a native input. Felte relies on native inputs. You can use createField (by creating your own "wrapper" Svelte component that will render your ) or... better yet... you can experiment with what I've been working for the past weeks.
-
Creating a Chai like assertion library using proxies
For the past few weeks I’ve taken the (arguably pointless) work of migrating Felte from using Jest to uvu. This is a really tedious work by itself, but one of details that would have made this work even more tedious is that Jest prefers assertions to the style of expect(…).toBe* while uvu gives you freedom to choose any assertion library, although there’s an official uvu/assert module that comes with assertions to the style of assert.is(value, expected).
-
Announcing Felte 1.0: A form library for Svelte, Solid and React
After more than a year of work, I am proud to announce the release of version 1.0.0 of Felte!
unocss
-
Tailwind CSS v4.0.0 Alpha
I wish tailwind would support attributify like https://github.com/unocss/unocss, which is much more readable for complex layouts:
link
- UnoCSS — an Instant On-Demand Atomic CSS Engine
-
Catalyst – Tailwind CSS Application UI Kit
I feel the same about people praising Tailwind.
Tailwind (and similar, I tend to use https://unocss.dev/) is not good for your frontend architecture BUT they allow you to be so fast, that it negates the benefits.
For a job well done, I'd follow the principles of https://maintainablecss.com/
-
What do you think we can do better to improve Vue position in the frontend space as a dominant UI framework?
I think UnoCss is may be better than Tailwind already and has a good Vue integration https://unocss.dev/
-
~~New~~ Old way to write CSS
The most popular tools that implement this approach are: Tailwind, WindiCSS, UnoCSS.
-
Which is best for DX and efficiency, TailwindCSS, UnoCSS, PandaCSS, or the new MasterCSS
- UnoCSS: https://unocss.dev/
-
A design system for the federal government
haha, fair point. Still, I'm on the fence about how utility components are namespaced in USWDS. Perhaps giving users the flexibility to define the namespace might work better? One thing that bugs me is the absence of class-sorting like we have in TailwindCSS. Plus, there are some gaps I've noticed in USWDS. The naming, especially when comparing "padding-x-2" and "p-x-2", can be really annoying when switching around, maybe that could also be an option for the developer or project. Similar to the ideas antfu has on uno.css https://unocss.dev/ ♥
-
Modern CSS Framework or Library for Static Websites?
UnoCSS is a popular option
-
Vrite Editor: Open-Source WYSIWYG Markdown Editor
UnoCSS — for styling with Tailwind-like atomic CSS;
-
Why I Switched From Neovim to VSCode
Some exceptional libraries and frameworks only support VSCode, which you could argue is a bad thing, but it makes sense, VSCode is the most popular code editor after all. For example UnoCSS only has a VSCode extension, and it's my favourite way to write CSS. Astro has a LSP but I've found that the experience in VSCode is much better than in Neovim.
What are some alternatives?
Superforms - Superforms is a SvelteKit library that helps you with server-side validation and client-side display of forms.
Tailwind CSS - A utility-first CSS framework for rapid UI development.
svelte-use-form - The most compact reactive form controller (including Validation) that you'll ever see.
windicss - Next generation utility-first CSS framework.
svelte-formify
tail-kit - Tail-kit is a free and open source components and templates kit fully coded with Tailwind css 3.0.
skeleton - A fully featured UI toolkit for Svelte + Tailwind. [Moved to: https://github.com/skeletonlabs/skeleton]
unplugin-vue-components - 📲 On-demand components auto importing for Vue
wordle - A recreation of the popular game Wordle with additional modes and features. Made with Svelte in Typescript.
Quasar Framework - Quasar Framework - Build high-performance VueJS user interfaces in record time
material-web - Material Design Web Components
vanilla-extract - Zero-runtime Stylesheets-in-TypeScript