The Front-End ecosystem is becoming increasingly specialized and diverse, leading to higher complexity. This isn't surprising. I tend to reduce dependencies whenever possible, aiming to expand areas that don't change within the standard.
The Page Visibility API, as the name suggests, allows you to determine whether a page is currently visible to the user. More precisely, it tells you if the page can be seen on the monitor. There's no way to know if the user has their eyes closed or is looking elsewhere :)…
Web storage, consisting of sessionStorage and localStorage, is now very familiar. Unlike cookies, which were difficult to handle, web storage clarifies its use as client-side storage and has already become our friend with better usability.
Every time I start a frontend project, there are things that need to be decided. Defining the development environment and stack, choosing a version control tool (usually Git), deciding how to manage branches, determining the versioning strategy, and so on.
While developing, you frequently encounter red error messages due to mistakes in the code. It's fortunate if bugs are found during development, but seeing an error message in a live service can make a developer cringe and break out in a cold sweat.