Closed
Description
npx --yes [email protected] build
fails in my next project because I used a
icon.tsx
as favicon per the documentation
Removing icon.tsx
and adding icon.png
worked around the issue.
(As a note, icon.tsx
worked in dev
mode and showed a favicon as expected.
Error:
Bundling middleware function...
Bundling static assets...
Bundling cache assets...
node:fs:456
return binding.readFileUtf8(path, stringToFlags(options.flag));
^
Error: ENOENT: no such file or directory, open '/Users/bebbi/code/landing/.next/standalone/.next/server/app/icon/route.js.nft.json'
at readFileSync (node:fs:456:20)
at computeCopyFilesForPage (file:///Users/bebbi/.npm/_npx/243dd04f789c84f7/node_modules/open-next/dist/build/copyTracedFiles.js:39:42)
Possibly some relation to sst/ion#335
This came from this sst v3 issue
Metadata
Metadata
Assignees
Labels
No labels