How to develop component library which can easily adapt multiple design languages

• Mux Player: Customize the look and feel
• React Aria
• React Spectrum

Design the React component library

Seeking advice on optimizing website hosting for SEO with Remix.

• Search Engine Optimization on EpicWeb.dev
• How I built a modern website in 2021
• I Migrated from a Postgres Cluster to Distributed SQLite with LiteFS
• Fly.io
• PartyKit

Hi Kent!

How do you create a progress bar for actions in Remix?

Like if a request takes maybe 10 or 20 seconds to finish and you want to give your users some feedback that things are progressing?

Best regards,

When we were building client side application mocking during e2e tests was a bit easier because you could just monkey patch fetch and call it a day. Today we also control the server so the line has a bit shifted. There are solutions, like MSW, to mock on the server side too but what if instead of an API call you query a db?

The content for new developers is everywhere, but finding quality insight that helps you level to senior and above is hard to come by. This is in part because such content is difficult and time consuming to make. What goes into making such content and is there a lack of it in our industry?

Hi Kent,

It's Jan 👋

When creating a dropdown menu (e.g. to pick a role in an organization), would you wrap the whole menu in a form tag and then render multiple buttons within that form (one for each role)? Or would you render multiple forms (one for each role) with each having their own submit button?

Thanks a ton if you answer!

Best regards,

Hi Kent,

It's Jan.

I'm currently working on implementing toasts in a Remix app. I was using the Epic Stack as a reference.

BTW, thank you for creating it, it's so nice to take some features and functionalities from it when you need them!

Anyways, it looks like the implementation of the toast in the Epic Stack does NOT work with JavaScript disabled. But theoretically, you could make toasts in Remix progressively enhanced by giving the close button a form and prevent default when JavaScript is enabled.

It looks like the library you're using in the Epic Stack - Sonner - does NOT expose the close button, so you can't progressively enhance it.

Was it a conscious decision to make the toast JavaScript only? Or let me ask the decision more openly, what are your thoughts on this?

As always,

So, recently I started looking for my first software job. The first offer I received was from a company looking for an intern. The internship had the following conditions: 1) the first 3 months of it are unpaid 2) you have to sign a contract after the 1st month of it that obligates you to stay at the company 2 years after the internship is ended. I rejected it because I felt like you never know what that company may turn out to be. For example, it may try to exploit you and pay you the bare minimum for the job you're doing preventing your career growth and your only option may be to wait for that contract to expire and then start looking for a higher position at another company. I'd like to ask your opinion about:

My question is around the optimization techniques that a lot of people apply to React apps. I see very often how devs focus on executing their components only once or twice. What I think matters at the end is if there any changes in the actual DOM tree. If not they in theory should be ok to see your functional components fired many times.

Is Data Structures and Algorithms is necessary to become a successful full-stack engineer?