Steven

Why is this being removed?

If the command is going to be removed, it would be great if the algorithm itself was documented.

I see. I guess the confusing part is that untracked is the default selection (all users) but the chart doesn’t represent that, only tracked. So perhaps when all users is...

I really like TypeScript but I'm not sure how to integrate it properly besides using something like [node-ts](https://github.com/TypeStrong/ts-node). Is that what you are suggesting?

https://nextjs.org/showcase is using `next/future/image` which is unaffected by your PR (your PR is changing `next/image`). This sizer is svg and designed to prevent layout shift with `next/image`. Note there is...

This is fixed in Safari Tech Preview 154 https://webkit.org/blog/13207/release-notes-for-safari-technology-preview-154/#:~:text=Stopped%20painting%20a%20border%20for%20images%20with%20loading%3D%22lazy%22%20before%20it%20loaded https://developer.apple.com/safari/technology-preview/

I was wondering why the repo setting didn't work until I saw the notice added in https://github.com/refined-github/refined-github/pull/6019 I agree, I think `sync-pr-commit-title` and `clear-pr-merge-commit-message` should be disabled by default so...

One of the few image libs that did support wasm (`squoosh`) is [now deprecated](https://github.com/GoogleChromeLabs/squoosh/pull/1266#issuecomment-1208149979) and doesn't support node 18. So it would be great to get wasm support in `sharp`...

> show the reason a given yarn, npm, or pnpm is chosen That could be helpful: show which package.json was used. I'm wondering if that should be added to `DEBUG=corepack`...

Yes, it only works with Node.js 14 - See upstream issue here https://github.com/alixaxel/chrome-aws-lambda/pull/274 - Also see our alternative solution here #226