Steven

I created a PR here: https://github.com/nodejs/citgm/pull/1044

@guybedford Perhaps its best to move this proposal from [WHATWG](https://whatwg.org) (browser focused) to [WinterCG](https://wintercg.org) (server focused). Its becoming relevant again now that Node.js has [deprecated `url.parse()`](https://github.com/nodejs/node/pull/44919) which works with relative...

@lydiahallie @leerob This appears to be causing failures for a popular OSS project called RSSHub https://github.com/DIYgod/RSSHub/issues/11647#issuecomment-1410789482

This issue is that [your repo](https://github.com/testerez/test-next-sharp-import-error) has both [`yarn.lock`](https://github.com/testerez/test-next-sharp-import-error/blob/606f9e79192cbf0f538dbdd60b6a4698d9c976b8/yarn.lock#L2) and [`package-lock.json`](https://github.com/testerez/test-next-sharp-import-error/blob/606f9e79192cbf0f538dbdd60b6a4698d9c976b8/package-lock.json#L4) so yarn will be used. Since `sharp` dropped support for `yarn@1`, its expected to fail. If you delete `yarn.lock`...

@rusakovic There was another issue with pnpm specifically that was fixed in `next@canary` so please give that a try.

The memory leak seems to only be present when running in [`ubuntu:jammy`](https://github.com/jaunruh/next-image-test/blob/0dfdcf3bc88cc6767ec83831872bff313f03314e/Dockerfile#L1) base image (glibc). I don't see the memory leak when using the the recommended [`node:18-alpine`](https://github.com/vercel/next.js/blob/77ade436667566444defb80dd1a0e7183e4faff1/examples/with-docker/Dockerfile#L1) base image (musl)....

That repo is missing sharp. You need to run “npm install sharp” for production.

More related projects here: https://github.com/styfle/awesome-desktop-js

~~I just confirmed this was fixed in https://github.com/npm/npm-install-checks/pull/54 and https://github.com/npm/npm-install-checks/pull/57 which landed in [`[email protected]`](https://github.com/npm/cli/releases/tag/v9.6.5), so I think this can be closed~~ Update, seems to be not working.

@wraithgar I think we should reopen this issue. The original post says that the libc field should be used to avoid postinstall by only installing the correct optionalDendencies. I just...