Pooya Parsa

(note for myself) some nice investigation by @jasenmichael https://github.com/unjs/h3/pull/605#issuecomment-1910787078 most intrestingly that it seems to be reproducable only with Nuxt3 (maybe because of browser request?)

This issues seems to be fixed in latest Node.js versions from multiple reports. If after upgrading to latest LTS version of Node still facing issues please ping.

It will be added as a dev option to image.rules (warning or error)

It is not a security matter for jiti's usage of md5 in cache entry paths and a false-positive in that tooling.. We cannot easily change the default hash but we...

Mainly legacy decisions in jiti and if we change it will cause stall caches for lots of files for lots of users which makes chage tricky. If we can auto...

@denver-HJS I still can't reproduce since can't have access to a node-fips image with 18,20 version.

Can't progress on this without access to a runnable image. If you can provide a oneliner snippet that can stabily detect FIPS builds (maybe `process.versions` can have some hints), I...

we can make jiti to auto switch to different hash. I still have to try @tuckergordon shared image but if anyone intrested to move it forward, it should be a...

The main thing is that with Nuxt, you need to install `nitropack` as a dependency to allow typescript augmenting it properly. Nuxt could also provide a reexport /cc @danielroe wdyt?

c12 config (controlled by `nuxt` for example). Yes we need a `defuFn` wrapper to use consistently every place in c12, that extends `defuArray`-like behavior and allows overriding behavior per-key with...