What caused the Remotion Vercel Sandbox bugs?

Two issues: relative paths resolving wrong due to CWD shifts, and public/ subdir breaking flat sandbox uploads. Both silent until prod meltdown.

How do you fix relative paths in Node build scripts?

Use `path.resolve(__dirname, '../your-dir')` or ESM's `import.meta.url`. Ditch relatives — CWD lies.

Should you suppress errors in Vercel builds?

Never for prod-critical steps. Let deploys fail loud. Green builds hiding slowness

⚙️ DevOps & Platform Eng

Two Sneaky Bugs That Killed Our Remotion Vercel Sandbox

Build scripts promised speed. Delivered silence and slowness instead. Here's how two tiny bugs turned a slick Remotion Vercel Sandbox into a production nightmare.

DevTools Feed Apr 03, 2026 4 min read

Read in: Deutsch English Español Français Italiano 日本語 한국어 Português (BR) Русский Türkçe

Code diff fixing Remotion Vercel sandbox relative path bug

⚡ Key Takeaways

Anchor all paths to __dirname — relatives fail in Vercel envs. 𝕏
Remotion bundles copy public/ folders; delete or disable before sandbox upload. 𝕏
Remove error suppression in builds: fail fast over silent degradation. 𝕏

Published by

DevTools Feed

Ship faster. Build smarter.

#Node.js paths #Remotion #Vercel Sandbox #build scripts

Worth sharing?

Get the best Developer Tools stories of the week in your inbox — no noise, no spam.

Originally reported by dev.to

⚡ Key Takeaways

The 60-Second TL;DR

DevTools Feed

Share this article

Worth sharing?

Related Stories

Dead Code Erased $440 Million from Knight Capital in Just 45 Minutes

Terraform Secrets: The State File Trap No One Talks About

Containers: Just Processes, Kernel-Constrained

Docker for Beginners: Containers That Ship Code Like Cargo Ships

Stay in the loop