Introducing Valibot, a < 1kb Zod Alternative
I am pleased to announce, with support from Miško Hevery and Ryan Carniato, my new open source project Valibot. Valibot is a schema library for validating structural data, comparable to Zod, Ajv, Joi, and Yup. The big innovation of Valibot is the modular design of the API and an optimization of the source code for compression. This new approach enables unprecedented bundle size minimization throug
Qwik Reaches v1.0
The Qwik team is excited to announce that Qwik has reached v1.0. Qwik is a full-stack web framework that brings a fundamentally new approach to delivering instant apps at scale! Frameworks such as React, Vue, Angular, Svelte, SolidJS, and their meta frameworks (Next.js, Nuxt, SvelteKit, SolidStart, Astro) have revolutionized web development by providing powerful tools and abstractions that simplif
A Better Way to Use CSS in Web Applications
In this article, I want to discuss the kinds of properties that make working with CSS hard and the kinds of properties developers want out of the system. We will then analyze common solutions and how they stack against these goals. Finally, I will propose a solution that checks off all the boxes. Like so many other things on the web, CSS was designed for documents, not applications. As such, the d
Everything you didn’t know you need to know about buttons
Let’s start by making one thing clear — you should not use a div for a clickable element (at least in 99% of cases). But why? Simply put, a div != a button. A div is simply a generic container, and is missing a number of qualities that a properly clickable element should have, such as: Divs are not focusable, for instance, your tab key will not focus a div as it will for any other button on your d
Introducing Qwik City Server Functions
Today we are thrilled to show what the Qwik Core Team has been working on: Data Loaders: reactive low latency data loading in the server. Form Actions: run server code on user interaction export const useGetServerTime = loader$(() => { // This code runs in the server return new Date(); }); export const useAddUser = action$(async (user) => { const userID = await db.users.add(user); return { success
useSignal() is the Future of Web Frameworks
The key difference between Signals and State is that Signals return a getter and a setter, whereas non-reactive systems return a value (and a setter). Note: some reactive systems return a getter/setter together, and some as two separate references, but the idea is the same. The issue is that the word State conflates two separate concepts. StateReference: The state-reference is a reference to the s
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Resumable React: How to Use React Inside Qwik
Code Extraction: The Silent Web Revolution
Why useEffect May Not Be the Best Abstraction
Safe Data Fetching in Modern JavaScript