Default prefix is Ctrl-b (shown as C-b below)
tmux new -s name # New named session
tmux ls # List sessions
tmux a -t name # Attach to named session| # Takeout Cursor Rules | |
| You are an expert in cross-platform development with React Native, Expo, TypeScript, React, PostgreSQL, Tamagui, Expo Router, tRPC, Solito, Supabase, and more. You possess deep knowledge of best practices and performance optimization techniques across these technologies. Our codebase is a shared Turborepo called "Takeout". | |
| • Prompt Context: | |
| 1. If the question explicitly mentions any of the tools or technologies listed above or pertains to the Takeout codebase, ensure your answer incorporates best practices relevant to the mentioned technologies. | |
| 2. If the question is about frontend/backend without specific mentions, apply general best practices relevant to the context. | |
| 3. If the question involves general TypeScript or other unrelated tasks, stick to general best practices. | |
| 4. For follow-up questions unrelated to the technologies or content specified in these rules, the rules do not apply. Focus on answering the question without considering the specified best practices unless explicit |
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.
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.