As of @sveltejs/adapter-vercel version 1.0.0-next.63, the build process employs the exported nodeFileTrace function from @vercel/nft to determine which modules throw errors, allowing the errors logged by the CLI to be displayed in a much cleaner manner.
Unfortunately, this causes the build to error out:
As of @sveltejs/adapter-vercel version 1.0.0-next.63, the build process employs the exported nodeFileTrace function from @vercel/nft to determine which modules throw errors, allowing the errors logged by the CLI to be displayed in a much cleaner manner.
Unfortunately, this causes the build to error out:
Per @Rich-Harris, this appears to possibly be an issue within the exported nodeFileTrace function in @vercel/nft.