import { useEffect, useState } from "react"; import axios from "axios"; import "./App.css"; import InfiniteScroll from "react-infinite-scroll-component"; import CharacterCard from "./components/Card"; function App() { const [characters, setCharacters] = useState([]); const [page, setPage] = useState(1); const [hasMore, setHasMore] = useState(true); const [totalPages, setTotalPages] = useState(1); const fetchData = async () => { if (page == totalPages + 1) { setHasMore(false); return; } // <-----------------------------------------------> // waiting for 1 second before fetching data to show loading spinner, you can skip this await new Promise((resolve) => setTimeout(resolve, 1000)); // <-----------------------------------------------> const res = await axios.get( `https://rickandmortyapi.com/api/character?page=${page}` ); setCharacters((prevPosts) => [...prevPosts, ...res.data.results]); setTotalPages(res.data.info.pages); setPage((prevPage) => prevPage + 1); }; useEffect(() => { fetchData(); }, []); return (

Rick and Morty characters!h1> Loading...h4>} endMessage={

Yay! You have seen it allb> p> } > {/* Map over characters array and return JSX */} {characters.map((character, index) => ( ))} InfiniteScroll> div> ); } export default App;

This project was conceived as a coding challenge and a demonstration of integrating modern web technologies into a cohesive application. The core of this project involves leveraging GraphQL to interact with the open-source Rick and Morty API, a task I often set for potential hires.

export const apolloClient = new ApolloClient({ uri: "https://rickandmortyapi.com/graphql", cache: new InMemoryCache({ typePolicies: { Query: { fields: { characters: { keyArgs: false, merge(existing: Characters, incoming: Characters) { return { ...incoming, results: [ ...(existing?.results || []), ...(incoming?.results || []), ], } satisfies Characters; }, }, }, }, }, }), });

Hello, my fellow CS students! Are there any Rick & Morty fans here? Because I've just created an app called Portalpal for my final project. It's a fun little app designed to explore the Rick & Morty universe. With Portalpal, you can view, search, paginate, and filter characters. Additionally, you have the option to filter characters by episodes and locations. For the data, I utilized the rickandmorty API, which you can check out here: https://rickandmortyapi.com/. If you'd like to give it a try, here's the link to my app: https://portalpal.vercel.app/. I built it using React 18, and it took me about a month. I'm really proud of how it turned out! If you're interested, you can also find the source code for the app on my GitHub repository: https://github.com/kyawzinhtett/portalpal. Feel free to open an issue if you discover any errors.

Just a small app consuming the Rick and Morty API showing some basic stats of each character such as last known location, species and what episode(s) they appear in.

Checkout https://rickandmortyapi.com and their https://rickandmortyapi.com/graphql

Click the guys name in the footer. It’ll take you to his GitHub profile. There you can find the source code to the site and the API.

I'll be using Material UI for styling the cards. You can install it by visiting the Material UI installation guide.

For the UI, MUI is a huge time saver. It's open-core and thoroughly excellent: https://mui.com/

They also have a lot of pre-built dashboards that tie into various cloud vendors (typically not FOSS though).

(My opinion only, please treat it as just one person's thought process, not some eternal truth)

As a frontend dev, for me it's primarily just an ecosystem thing. There's nothing wrong with HTMX or any other solution, like Ruby on Rails or Hotwire or even other JS frameworks like Angular or Gatsby, but they are not really what I see in the majority of the web dev ecosystem.

By ecosystem, I mean this:

- Developers are easy to find & hire for, and can work on existing code without much training because there are (relatively) standardized practices

- For any common problem, I can easily reuse (or at least learn from the source for) a package on NPM

- For any uncommon problem, I can find multiple robust discussion about it on various forums, Stack, etc. And ChatGPT probably has a workable overview.

- I can reasonably expect medium-term robust vendor support, not just from the framework developers but various hosts, third-party commercial offerings (routers, state management, UI libs, CMSes, etc.), i.e., it's going to stay a viable ecosystem for 3-5 years at least

- I don't have to reinvent the wheel for every new project / client, and can spin up a working prototype in a few minutes using boilerplates and 1-click deploys

I've been building websites since I was a kid some 30 years ago, first using Perl and cgi-bin and then PHP, and evolved my stack with it over time.

I've never been as productive as I am in the modern React ecosystem, especially with Next or Vite + MUI (https://mui.com/). Primarily this is because it allows me to build on top of other people's work and spend time only on the business logic of my app, at a very high level of abstraction (business components) and with a very high likelihood of being able find drop-in solutions for most common needs. I'm not reinventing the wheel constantly, or dealing with low-level constructs like manually updating the DOM. Or worse, dealing with server issues or updating OS packages.

What used to take days/weeks of setup now takes one click and two minutes, and I can have a useable prototype up in 2-3 hours. Because 95%+ of my codebase isn't mine anymore; I can just reuse what someone else built, and then reframe it for my own needs. And when someone else needs to continue the work, they can just pick up where I left off with minimal onboarding, because they probably already have React knowledge.

I think React, for all its faults, has just reached a point of saturation where it's like the old "nobody ever got fired for buying IBM", i.e., it's a safe, proven bet for most use cases. It may or may not be the BEST bet for any project, but it's probably good enough that it would at least warrant consideration, especially if the other stacks have less community/ecosystem support.

Explore Material UI: Material UI Documentation

- UI kit (I personally have good experience with React Material UI - https://mui.com/; there is also https://tanstack.com/)

the network is settled (I got the code from some discussion group). But nothing works. Playwright has also

page.waitForLoadState({ waitUntil: "domcontentloaded" }); etc.

but they are not working for my test cases.

2)

I have noticed that https://mui.com/ have dropdown menus, which implementation is far from normal html option. Mui uses some kind

MUI | Remote UTC-6 to +5 | Multiple roles | Full time | https://mui.com/

I'm a co-founder and the CEO of MUI. Our objective in the short term is to become the UI toolkit for React, unifying the fragmented ecosystem of dependencies into a single set of simple, beautiful, consistent, and accessible React components. In the longer term, our goal is to make building great web UIs quicker, simpler, and accessible to more people through a low-code platform for developers.

Some things we’re proud of:

- 25% of the downloads that React receives.

- 1M developers on our documentation every month.

- Solid financials: profitable

If this sounds interesting to you, we are hiring for: UI Engineers, Product Engineers, Developer Advocate / Content Engineer:

Here, at Woovi, our design system has been wrote using [MUI](https://mui.com/. But, in my opinion, I have some pain points considering how MUI built their components, most focusing on the fact of how they expose their component APIs and how they handle the component structure.

My feeling as a frontend dev was that Material Design You is just run of the mill enshittification at Google. Around the time that came out, Google also started to hide more buttons in the UI, made the drop down shade much more clumsy, got rid of the excellent Pixel fingerprint scanner, etc.

It felt to me like some other busy body design team had to show innovation and so made Material You adopt your wallpaper colors (in some ugly variation). It was like the MySpaceification of Android.

Material Design spawned some of my favorite projects, like MUI: https://mui.com/

That tracks Material v2 (pre you) and IMO is the best web UI currently available. There's some tentative work on adding Material You, but I hope they don't. It's a step backward IMO, form over function and against the original spirit of Material as a usability design library. https://github.com/mui/material-ui/issues/29345

5.material-ui