It may be ran by Google, but https://web.dev/ is one good source for keeping up with new web technologies. - Source: Hacker News / about 1 month ago

“If the sanitization logic in DOMPurify is buggy, your application might still have a DOM XSS vulnerability. Trusted Types force you to process a value somehow, but don’t yet define what the exact processing rules are, and whether they are safe.” — this caution from web.dev makes me want to play around with TrustedTypes more and get a better understanding. - Source: dev.to / 3 months ago

Before we start creating pages in our application, it's important to understand how Next.js renders content. The framework supports multiple rendering methods including server-side rendering (SSR), static site rendering (SSG), and client-side rendering (CSR). There are many pros and cons to each rendering method (too many to cover in this post) so if these concepts are new to you, Google’s web.dev site has a very... - Source: dev.to / 9 months ago

The lifecycle of an interaction. Source: web.dev. - Source: dev.to / 5 months ago

Probably not, it's the CSS used so far, so if there are elements you've not interacted with, that's an issue. This web.dev article gives some tools you can use https://web.dev/articles/extract-critical-css. Source: 7 months ago

That's why I've added trial tracking to https://everlint.com/. Source: over 2 years ago

If you export your transactions to a CSV file, you can use https://everlint.com to analyze it for subscriptions. Source: almost 3 years ago

Never forget an autorenewing subscription again: https://everlint.com Hosted on a simple Debian Linux VPS with https://tilaa.com. Running nginx with Let's Encrypt certs. Built in Ruby on Rails with PostgreSQL for the database and Stimulus as JavaScript framework. Charts are generated with ChartJS and CSS is using Bulma framework. - Source: Hacker News / almost 3 years ago