Node in the Browser × WebContainers + NodeBox
In this Hasty Treat, Scott and Wes talk about two new services that allow you to run Node in the browser, WebContainers + NodeBox. Why Node in the browser? How does it work? And what are the differences and limitations of the services?
If you want to know what’s happening with your code, track errors and monitor performance with Sentry. Sentry’s Application Monitoring platform helps developers see performance issues, fix errors faster, and optimize their code health. Cut your time on error resolution from hours to minutes. It works with any language and integrates with dozens of other services. Syntax listeners new to Sentry can get two months for free by visiting Sentry.io and using the coupon code TASTYTREAT during sign up.
- 00:25 ">00:25 Welcome
- 01:14 ">01:14 Sponsor: Sentry
- 02:45 ">02:45 Webcontainers and NodeBox
- Introducing WebContainers
- Code Sandbox
- GitHub Codespaces
- 06:42 ">06:42 Why Node.js in the browser?
- 11:08 ">11:08 How does it work?
- 13:10 ">13:10 Clientside APIs
- 14:27 ">14:27 Using iFrame to proxy messages
- 17:39 ">17:39 Are these open source?
- 19:22 ">19:22 Differences between the two services
- 21:10 ">21:10 Wes to Figma, Scott to Penpot
- 24:51 ">24:51 Limitations