Bookmarks

Discover more about what's new at AWS with Amazon S3 no longer charges for several HTTP error codes

Simplifies screenshots creation process.

A browser extension that allows you to monitor, intercept, and debug JavaScript sinks based on customizable configurations. - GitHub - kevin-mizu/domloggerpp: A browser extension that allows you t...

node:test runner wrapper with TypeScript support.

A simple checklist of the essential items to include in your bug reports.

Screen reader driver for test automation.

Reliable automation for your screen reader accessibility test workflows with Guidepup. Drive VoiceOver and NVDA a11y tests with ease

A simple JavaScript tool for converting any layout you have to drag-to-swap layout

✨ A framework-agnostic tool that converts any layout into a drag-to-swap one with just a few lines of code https://swapy.tahazsh.com/ - TahaSh/swapy

Regex template tag for readable, high-performance, native JS regexes, with context-aware interpolation and always-on best practices - slevithan/regex

Turn any webpage into structured data using LLMs.

Extensible DNS libraries written purely in Haskell - kazu-yamamoto/dnsext

Since the dawn of computing, humans have sought to estimate how long it takes to build software, and for just as long, they've consistently failed. Estimating even medium-sized projects is devilishly difficult, and estimating large projects is virtually impossible. Yet the industry keeps insisting that the method that hasn't worked for...

💥 Blazing fast terminal file manager written in Rust, based on async I/O. - sxyazi/yazi

Blazing fast terminal file manager written in Rust, based on async I/O.

Migrating the Miru app from Sidekiq to SolidQueue eliminated the dependency on Redis, reducing costs by utilizing database for job storage.

When testing and monitoring websites end to end with Playwright, choosing the right locators is crucial. Proper locators help create tests that are less flaky and more reliable. Let's explore user-first locators and how to filter locators for more robust tests. Example Scenario Consider a simple web page with a headline, a button, and a status update box. Clicking the button updates the status and throws confetti. Here's how we can test this. Why we don't want to find a page element with CSS selectors If you're used to some older systems for automation and page manipulation like JQuery, we might be tempted to use CSS selectors. If we inspect this page we'll find, sure enough, that there is a class applied to this button that should select it in the page. We could click this button in a test with a line like await page.locator("button.button-frontpage-style").click() and that would work, but it's not recommended. What is the problem with this approach? Our users look at the page and want to find a button, they don't look for a CSS class, so our test is no longer emulating a user path. If a frontend engineer changes the class for style reasons to read button-hero-panel-style then our test will return a false positive: showing a problem where there is none. If our button text is coming from a CMS, and it breaks, the button text could change to "HEROBUTTON_TXT" and our test would still pass, despite the UI being broken for the user, a false negative. Due to the reasons above, the Playwright project encourages you to not use CSS locators, and it's a good idea to follow the standards set down in the project! Instead of CSS selectors, try User-First Locators Playwright offers a number of locators that are based on page role, a more functional view of the page than finding by CSS or HTML. Use built-in locators like getByRole, getByText, and getByLabel, which will all work the same in the test that they will for the user, even if the user is using an unusual browser build,...

rubocop-todo-corrector で .rubocop_todo.yml を撲滅する STORES でソフトウェアエンジニアをやっている @morihirok です。 先日 【増枠】10年超えRails開発の振り返りと未来 - 持続可能な開発の具体策 というイベントで STORES の Rails 開発に…

Trivial packages, while convenient, can introduce significant risks such as dependency bloat, security vulnerabilities, and performance issues in mode...

Node.js で型安全な環境変数を扱うスニペットを作りました。

🧙 Valtio makes proxy-state simple for React and Vanilla - pmndrs/valtio

Introduction There was a discussion in our team after releasing Zustand v3 and the brand new Jotai. It was about whether we could develop another library for global state. In this post, I will reflect on the start of Valtio’s development and its API design. Hesitation at First While the idea of a proxy state sounded promising, I was hesitant to develop a third global state library at first. We were already maintaining two libraries in the same problem domain.

I am loving this API for working with React state. It’s a very light wrapper around useState. I call it useStateObject.

How to use tRPC with React for full-stack type safety with TypeScript ...

How I set up my new M1 MacBook Pro as a web developer in 2024 for web development ...