Mahad Kalam SkyfallWasTaken

Stuff I wish I'd known sooner about service workers

I recently had several days of extremely frustrating experiences with service workers. Here are a few things I've since learned which would have made my life much easier but which isn't particularly obvious from most of the blog posts and videos I've seen.

I'll add to this list over time – suggested additions welcome in the comments or via twitter.com/rich_harris.

Use Canary for development instead of Chrome stable

~~Chrome 51 has some pretty wild behaviour related to console.log in service workers. Canary doesn't, and it has a load of really good service worker related stuff in devtools.~~

https://github.com/nikteg/TDA602/blob/f1693d2e00d3929f4b693e3a201754519e4f85ef/project/apps/se.isakpersson.dashyknight/payloads.txt :

CjoKGnNlLmlzYWtwZXJzc29uLmRhc2h5a25pZ2h0GhxMdGh4b0J2OTZ4VW5RYTU0d3Nic1NuaHFBR1k9EiAdDJ1K7i2rbUrFMRD/TrQvB+/XtjGG0gV1BavLZ9rUwRjXqa7Z0aKp3zog7Ne+9szA8at7

https://github.com/4kumano/reftoken/blob/99d1d980c0015c8b1113cb65b02ee0ede96ae471/sumber.txt :

CjoKGmFwcC5nZXRsb2FkZWQuYml0Y29pbmJsYXN0Ghw2Wmk4VHdRTnlpT0QrdXMyNC81YVlwd3h0NUE9GLingOeJmKD6Ng==

What to evaluate and consider before adding usage of new third-party crates.

These are not exact requirements but questions to investigate and discuss to help reason around the health, safety, maintainability, and more around crates.

This can also be read as an opinionated guide for crate authors of what our (Embark's) guidelines and recommendations are, though should not be taken too literally.

Legend: 🔒 Must have, ⭐️ Should have, 👍 Nice to have, ℹ️ Info

	use std::io;
	use std::ptr;
	use std::mem;
	use std::io::Error;
	use std::io::ErrorKind;
	use std::path::Path;
	use std::ffi::CString;

	use winapi::um::winnt::HANDLE;
	use winapi::um::memoryapi as wmem;

	# /// script
	# requires-python = ">=3.12"
	# dependencies = [
	# "asyncio",
	# "httpx",
	# ]
	# ///
	# Run this with `uv`: `uv run leave.py`
	import asyncio
	import httpx