Sebastian "Sebbie" Silbermann

> This might be solved in pnpm v9. Can confirm. We were facing the same error using `https://` protocols in package versions. After bumping pnpm from 8.15.0 to 9.4.0 the...

Cannot reproduce on Firefox 88.0.1 nor 91.01 with a viewport of 320x1280 when scrolled to the bottom and opening the Select. @mnajdova, @stevegreenn Can you still reproduce the problem? Could...

With a priority on customization we should use context by default. Even if it looks like a overengineered cloneElement for the basic case it prevents so much subtle bugs with...

> the main problem of the default exports is implicit renames. This is not a problem. It causes problem you later describe: > If we have an allowed implicit rename...

I don't see any concrete problems in this issue. I can only see hypotheticals that I don't agree with.

Can somebody explain to me why I have to rename every callsite if I rename the implementation? Doesn't the vscode refactor also keep the import name i.e. ```diff // components.tsx...

> You probably would like to search "FancyButton" and open the component source, right? 99% of the time the answer is no. The remaining 1% I do CTRL+Click in vscode...

> reading code not only in the editor What other methods are you trying to optimize?

> I have described everything in RFC I've read it again and I can't find mentions of the way you consume and work with code. Maybe I missed it. Could...

We should flatten this instead of allowing arbitrary options. We don't know if a passing all through will make sense. If people want to access the root options directly, they...