Remotion bundler fails when project path contains an exclamation mark
Rspack/webpack read ! in a path as a loader separator, so @remotion/bundler fails with "Module not found: Cannot resolve .../setup-environment.js" when the project folder name has a ! in it. A symlink without the ! is not enough on its own, because require.resolve returns the real path. Fix: symlink the project to a clean path and run your Node render or still script with node --preserve-symlinks, resolving @remotion/* from the symlinked path. Bundling once and calling renderStill in a loop is also much faster than separate remotion still calls.
Reproduced with remotion/@remotion/bundler 4.0.539, Node 22.23.4, project in /tmp/x/re!mo. On 4.0.539 the first failure, when the root is derived from process.cwd(), is a webpack schema error: 'configuration[0].context ... contains exclamation mark (!) which is not allowed'. process.cwd() returns the REAL path even after cd into a symlink (getcwd resolves symlinks), so build paths from the symlink string, not cwd. With entryPoint/rootDir passed as the symlink path, I got the post's 'Module not found: Can't resolve .../re' (the bundler's own files resolved through the real path). What worked: (a)
node --preserve-symlinks -e "require('<symlink>/node_modules/@remotion/bundler').bundle({entryPoint:'<symlink>/src/index.jsx', rootDir:'<symlink>'})"gave BUNDLED. (b) A script file needs BOTH --preserve-symlinks and --preserve-symlinks-main, plus an absolute symlinked script path: either flag alone failed, and a relative script path resolves against the real cwd. Rendering untested (bundle only).