open-wc VS React

npm init @open-wc@latest Need to install the following packages: @open-wc/[email protected] Ok to proceed? (y) y _.,,,,,,,,,._ .d'' ``b. Open Web Components Recommendations .p' Open `q. .d' Web Components `b. Start or upgrade your web component project with .d' `b. ease. All our recommendations at your fingertips. :: ................. :: `p. .q' `p. open-wc.org .q' `b. @openWc .d' `q.. ..,' See more details at https://open-wc.org/init/ '',,,,,,,,,,'' Note: you can exit any time with Ctrl+C or Esc ✔ What would you like to do today? › Scaffold a new project ✔ What would you like to scaffold? › Web Component ✔ What would you like to add? › Testing (web-test-runner) ✔ Would you like to use typescript? › Yes ✔ What is the tag name of your web component? … testing-components ./ ├── testing-components/ │ ├── .vscode/ │ │ └── extensions.json │ ├── demo/ │ │ └── index.html │ ├── src/ │ │ ├── index.ts │ │ ├── testing-components.ts │ │ └── TestingComponents.ts │ ├── test/ │ │ └── testing-components.test.ts │ ├── .editorconfig │ ├── .gitignore │ ├── LICENSE │ ├── package.json │ ├── README.md │ ├── tsconfig.json │ ├── web-dev-server.config.mjs │ └── web-test-runner.config.mjs ✔ Do you want to write this file structure to disk? › Yes Writing..... done ✔ Do you want to install dependencies? › Yes, with npm

Very much still a thing, https://open-wc.org/ is a good resource for examples and best practices.

I have this design system project for a company, I need to make web components and instead of using open-wc.org pre-built, I chose to go Vite.

Nice. We have data with meaning. Now let's create the presentation layer (aka the UI!) and then let's add interactivity to the UI, so we can have feedback when actually simulating an exam (aka the Frontend!). Since in ING we are advocates of Web Components, I always wanted to give this stack a try for side projects. I jumped right into open-wc.org and used the npm generator. Everything worked precisely as expected. It was a breeze since my Chapter is using lit every. single. day. So I could finally get some mileage myself, in writing lit. At work, as a Chapter Lead, I prefer to spend my time more effectively for the team, rather than coding new features by myself; my chapter does it better anyway (#proud).

I suggest following these best practices for creating a custom web element: https://open-wc.org/

Open Web Components is a great tool for accessing open-source web components and is very easy to set up with their quickstart guide and easy to understand documentation.

This application is one of many applications out there that are dipping their toes in the land of web components. Web components are still very new and ever-growing. While I have been developing on HAX-the-Web, I am also the Project Manager for HAXCamp 2022. < hax-camp > is an unconference dedicated to all things Web Components!This year's event is being student-run and we anticipate there being discussions about openwc, lit, performance, element composition, css, hax.psu, pedagogy, and design systems. If this work flow is something that you are interested in, I would encourage signing up for this event. It is much more than this, larger than you know and a way to connect with students, faculty, staff, and professional in the industry.

Early in my career, I struggled to understand how React’s state updates actually worked. Docs gave me the basics, but edge cases around batching were confusing. One weekend, I pulled up the React source code on GitHub and traced how state changes bubbled through the scheduler. Suddenly, the “weird bugs” I hit at work made sense because I wasn’t guessing anymore, I’d seen the engine.

3. Next.js and React (Frontend framework)

My primary passion is backend development, but I wanted to build a user-friendly frontend to complete this project. Given my experience with React, Next.js was the obvious choice due to its excellent documentation and ease of use.

Check out the React 19 Upgrade Guide for more details. Have fun coding, and share in the comments what you’re building with React 19! 🎉

React Official Documentation — Start here for official guides and tutorials

At IVAO, we partially follow micro-services best practices. This means each business group (e.g., Flight tracking, Flight planning, Air Traffic controlling, Training) has its own NestJS API and ReactJS frontend. But we took a shortcut on the DB side, as we have quite some references across systems, especially for user IDs, airports, etc... We decided to have a single MariaDB instance while having a dedicated logical database for each API, so we still have a separation of concerns but we can guarantee data integrity with foreign keys across those databases.

React.js (fast, large ecosystem)

Tools: V0 by Vercel, shadcn/ui, React, Tailwind CSS V0 turns natural language prompts into ready-to-use React + Tailwind UI code. Ask for “a responsive SaaS dashboard with a dark theme and collapsible sidebar” and you get production-ready code instantly, accessible, tweakable, and not locked into rigid templates.

My PR: https://github.com/facebook/react/pull/34116