Launching a Website with TypeScript Errors

14min Snip

00:00

Play full episode

Summary

Transcript

Episode notes

They discuss the concept of launching a website with TypeScript errors, arguing that it is not necessary to fix all the errors before launching if the code has been tested and works fine. They also discuss lessons learned and bug fixes during the launch, the importance of paying attention to type errors, and the need for basic end-to-end testing.

In this episode of Syntax, Wes and Scott talk about the lessons they learned while launching the new Syntax website including launching now, transcription bugs, error monitoring, black text on black backgrounds, and more.

Show Notes

00:10 Welcome to Syntax
01:41 Syntax Brought to you by Sentry
02:43 Don’t wait. Launch!
04:28 Transcript bug
Most Powerful Speech-to-Text API | Deepgram
09:01 Error monitoring is a must
12:36 Timestamp error
16:20 Black text on black background might hide things
17:33 WASM Vercel file system
21:18 Things have gotten easier to launch
PlanetScale: The world’s most advanced database platform — PlanetScale
23:36 Switching from OpenAI to Anthropic Claude and AI Responses aren’t always JSON
25:34 Local dev is fast
Navigation API
31:37 Mind your payloads
32:41 GitHub Milestones
33:57 Almost forgot the Robots.txt
36:17 Chron job timeout
Inngest
40:06 TypeScript errors don’t need to be zero to launch
42:25 GitHub Actions pipeline bug
43:23 Basic testing will do
Playwright
44:56 Have a designer to work with
Airbase
52:07 Sick Picks