Diego Muracciole

So I tried upgrading react's peer dependency from `^16.8.6` to `>16.8.6` that matches new React 17 version, but NPM v7 stills throws peer dependency errors due to `[email protected]` which has...

Just published `1.6.16` with the change suggested by @princefishthrower above, but I think it's not enough to make this whole peerDependency check to work. Please try it and let me...

Yes. As explained above, I couldn't find the way of keep supporting react 16 and 17. This whole peer dependency check in nvm@7 breaks this library. The issue is not...

Interesting.. But I don't think npm aliases can solve this. I will still have to list a `react-reconciler` version with a peer dependency of react@16, so the check will still...

Thanks @maxdev ! That might be right. Will try today and report back here

Unfortunately this still happens :(  npm keeps insisting on installing `[email protected]` even if `react@16` is present

Thanks @KarlBaumann. It is :( but as explained above I'm on a dead end for both supporting react 16 and 17 with the new npm peer dependency install

While I generally agree, with React for me it's more complex. Since it's the **main** peer dependency of this project and one of those libraries that people usually do not...

I don't have any fixed plan. I'm open to suggestions 😄 Would still love to see if there's some solution to this. @KarlBaumann releasing a 3.x it's not an option...

Cool! I didn't know that this can be done. This will require changes in the pdfkit layer, and a low-level research about how something like this can be done PDF-wise