Maël Nison
Maël Nison
Can't check right now, but I imagine they are missing a peer dependency, allowing packages to be duplicated between your dependencies and theirs.
On the bright side I can reproduce it - on the not-so-bright side since it used to work I have to assume it's a regression on Electron; I'll investigate to...
Yep, I agree. I actually [opened a thread on OpenCollective](https://github.com/opencollective/opencollective/issues/1625) some time ago to tell them that they shouldn't do this, but didn't get answers back then. The problem with...
My ideas so far are based on the following items: - We want to allow package authors to notify their existence to their users - We don't want to clutter...
No. NPM decided to change the behavior of `file:` dependencies some time ago to become symlinks, but we decided against that. Instead, `link:` dependencies are the recommended way to create...
https://github.com/yarnpkg/rfcs/blob/master/implemented/0000-link-dependency-type.md
Perhaps it's a separate bug in Next.js, it seems to always mangle everything: https://github.com/vercel/next.js/blob/684d11bfc9fd491102c4f13168ff681df6001952/packages/next/src/server/dev/hot-reloader-turbopack.ts#L277
Yes; since React thinks the updated files are fine to HMR, it prevents the HMR to bubble up and hit either the parent boundary or the live reload fallback. In...
Correct; it doesn't work either with `--webpack` but I haven't investigated to figure out why (whereas I used breakpoints to confirm that Next.js was incorrectly calling `module.hot.accept()` due to the...