svelte-adders VS dom-examples

Perhaps your tool can steal some inspiration from the following:

- svelte-add is a similar tool for Svelte(Kit) projects: https://github.com/svelte-add/svelte-add

- svelte-add was originally based on a more generic tool: https://preset.dev

- I actually find `npm create svelte@latest` sufficient most of the time. It's like a starter project with presets for most best practices.

Oof... Not gonna lie, that one looks rough. I would start with something simpler to get started with. Maybe pick one from here https://github.com/svelte-add/svelte-add

For this tutorial, I’ll show you how to use a utility package named svelte-add to handle the integrations.

If you're just learning SvelteKit, check this tool out: https://github.com/svelte-add/svelte-add

It will save you a ton of time by making it really easy to add integrations to your projects (like Tailwind, Bootstrap, Supabase, Jest, etc)

By the way svelte-add is a great tool to quickly add Tailwind and a bunch of useful tools to a project. Highly recommended! I'm always starting new projects to experiment and this thing saves me a lot of time.

Somewhat the documentation is confusing, IMHO. Maybe it is just me, however there is just too much configuration to be done. I've never figured out how to actually make it work after the latest release 0.7. Would love to have Houdini+KitQL in https://github.com/svelte-add/svelte-add . Just run a simple command like npx svelte-add@latest houdini-kitql with a prompt for graphql URL and done. All the configs added automagically

We'll use SvelteAdd to add TailwindCSS to our application quickly. Run the below command to add TailwindCSS to our project.

I've created a couple of example projects using the npm init command for both Vite and Svelte. Added in Tailwind support using Svelte Add and replaced the index page styles on each with Tailwind styles.

Fonte: MDN web docs

References MDN Chrome Docs

> if writing a browser today is in fact easier than both writing AND maintaining a browser a decade back.

Probably not. Yeah we have web standards and some idea of how to architect it, but the total set of APIs and HTML/CSS/JS features a browser supports is probably changing faster than the Ladybird team can actively implement it. The API surface is just impossibly large compared to 10 or 15 years ago. Look at all of these: https://developer.mozilla.org/en-US/docs/Web/API

I added polyfills for the Web APIs used in the React code.

In addition to pure JavaScript, there are hundreds of Web APIs documented at MDN. These APIs cover everything from the DOM to Web Workers with great detail.

I'm reading MDN Web Docs on Web APIs. There are two basic sections, specifications and interfaces.

The biggest difference is usually found in what non-ECMAscript standard JS web apis or features are implemented in different browsers. Here's a list of typical web APIs, and for many of them there is a compatibility table at the bottom detailing which browser do or do not support it. https://developer.mozilla.org/en-US/docs/Web/API

Documentation of Web APIs and interfaces is located on the MDN (Mozilla Developer Network) website. The term "Web API" can refer to browser or server APIs. In this article, it refers to Browser APIs.

The second one was an afternoon of "boredom." I wanted to develop, but I was running out of ideas. So, I decided to explore something new. I navigated to the Web APIs page on MDN, and something caught my eye on the letter g: Gamepad API.