As of a few versions ago, my app using intercepting routes with (…) produce an absolute system path instead of a relative one, which doesn‘t work for apps that were compiled on another path or system.

Example folder structure:

feed
[feedId]
(…)photo

Will resolve under the hood to an absolute system path from the runner, where the app was compiled (completely different machine / server setup), as evident by the error message telling me the path saying it wasn‘t found.

This seems to be a regression, previous builds worked just fine with the folder / routes setup.