Errors occurs when 'minimumCacheTTL' or 'icon.ico' are used with Turbopack

[Enkratia]

Link to the code that reproduces this issue

https://github.com/Enkratia/css-reload-show-2

To Reproduce

0. npm i

First error:

1. npm run dev:turbo
2. see error related with minimumCacheTTL (in terminal)

Second error:

1. comment minimumCacheTTL in nextConfig.images (in next.config.mjs)
2. npm run dev:turbo
3. open http://localhost:3000/
4. see error related with icon.ico (in browser)

Current vs. Expected behavior

1. When i add minimumCacheTTL: 31540000000 to nextConfig.images it gives an error:

• invalid value: integer 31540000000, expected u32 at line 54 column 34] {
  code: 'GenericFailure'

** Yes, minimumCacheTTL is not needed in dev mode, so i can just create 2 different next.config.mjs (for dev/prod mode), but this is working with webpack without any problems.
** minimumCacheTTL: 3154000000 is working fine (one zero less).
** It might be related to BigInt.

2. When i add icon.ico in app (as it is written here https://nextjs.org/docs/app/api-reference/file-conventions/metadata/app-icons) - i get this error:

Processing image failed
unable to decode image data

Caused by:

• Format error decoding Ico: The PNG is not in RGBA format!
• The PNG is not in RGBA format!

Expected behavior - no errors (these errors doesn't occur when webpack is used)

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Home Single Language
Binaries:
  Node: 20.10.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.2.6
  react: 18
  react-dom: 18
Next.js Config:
  output: standalone

Which area(s) are affected? (Select all that apply)

Turbopack

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

** Actually my Operating System is Linux MInt 21 Cinnamon Edition x64, but when i use: "npx --no-install next info", - i am getting an error: "npm ERR! npx canceled due to missing packages and no YES option: ["next@14.2.6"]"

** node version: v21.7.2

[samcx]

@Enkratia Thank you for submitting an issue!

I have shared this with the Turbopack team. We will be taking a look!

[bgw]

Large TTL Value

#69379 should fix the TTL issue by changing the u32 currently in use to a u64 (should support values up to 18446744073709551615).

Workaround: In the meantime, if you really want to set a TTL this large, just use u32::MAX, which is 4294967295. That should be sufficient for any practical purposes.

ICO Decode Error

This is because your icon.ico file technically isn't actually a valid ICO file!

$ file icon.ico
icon.ico: MS Windows icon resource - 1 icon, 256x256 with PNG image data, 256 x 256, 8-bit grayscale, non-interlaced, 32 bits/pixel

ICO files are required to be encoded with a RGBA/ARGB colorspace when using PNG image data:

The ability to read PNG images from ICO format images was introduced in Windows Vista.[7] A PNG image can be stored in the image in the same way as done for a standard Windows BMP format image, with the exception that the PNG image must be stored in its entirety, with its file header and must be in 32bpp ARGB format.[7]

-- https://en.wikipedia.org/wiki/ICO_(file_format)#PNG_format

This error comes from the image library we use:

• Purpose of DecoderError::PngNotRgba check image-rs/image#1590
• https://github.com/image-rs/image/blob/c8d67ecc2a9ba42bb105be8cd430bba4248ee974/src/codecs/ico/decoder.rs#L27-L28
• https://web.archive.org/web/20161102162735/https://blogs.msdn.microsoft.com/oldnewthing/20101022-00/?p=12473

While image-rs should be careful to only output valid ICO files with RGBA colorspace, it arguably should be more tolerant about what formats it accepts when decoding. We can work to upstream a change to image-rs, but that will take some time. I've created a backlog internal issue PACK-3221 for our team to track this.

Workaround: In the meantime, you should be able to encode your ICO file using RGBA colorspace, which should fix this issue, or you can save the file as a normal icon.png file instead of an icon.ico.

[Enkratia]

@samcx, @bgw ok, thank you, no more errors.

[github-actions]

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.