Warning: findDOMNode is deprecated outside StrictMode.

[keyboy21]

Hi, Has any updates to remove findDOMNode. In react 18.3 adds warnings for deprecate this API and in v19 will be removed.

thanks.

Prev related issue: #282

[MatthewHerbst]

Hey, thanks for raising this. I saw the patch notes the other day and was like, whelp, that's going to be a fun one 😄
I believe the change here might require us to make a breaking change to the type of our content prop. Not totally sure on that one. I'll look into this next weekend and report back. I wouldn't mind making a breaking change honestly, there are a few changes that I've been meaning to make for a while that would require a breaking change and this might finally be an excuse to do that

[RISHIKESHk07]

@MatthewHerbst @yusuf-saydullayev any update on this ?

[MatthewHerbst]

Currently working on v3 of this library which will introduce some long needed breaking changes that will also allow supporting React 19 properly. I expect to have a beta release out by the end of the weekend

[MatthewHerbst]

Removing findDOMNode is proving more challenging than I had expected. Getting the underlying DOM Element, not the React component wrapping it, is proving to be a PITA. Still working on this, delayed getting a beta out by a few days

[Dillpickleschmidt]

Removing findDOMNode is proving more challenging than I had expected. Getting the underlying DOM Element, not the React component wrapping it, is proving to be a PITA. Still working on this, delayed getting a beta out by a few days

Has the beta been released somewhere? I apologize if you're still working on it, just trying to make sure I'm not crazy for not seeing it anywhere since you wrote this 2 weeks ago.

[MatthewHerbst]

You're not crazy, I'm still fighting with it unfortunately, it's a pretty core change to how this library operates. Looking forward to the long weekend to get this over the finish line, at least with some sort of v3-alpha release

[MatthewHerbst]

Update: I went down a rabbit hole trying to also get an ESM build out finally as part of v3. I think I'm going to give that up for now and just push the fix for React 19, targeting getting a release out this evening unless I run into some other issue. Will keep y'all updated. It's just me on this project, so I appreciate everyone's patience

[RADesai]

Your efforts are appreciated @MatthewHerbst

[raffidahmad]

react-draggable has an alternative to findDOMnode by using the ref, maybe that could help?

[MatthewHerbst]

Alright friends, the day has arrived! Please give v3.0.0-beta-1 (npm install react-to-print@beta) a shot and let me know how it works for you. There are a signifiant number of breaking changes though they should be fairly straightforward to migrate. Feedback is massively appreciated. Thank you all for your patience

[Alexandredc]

Thank you @MatthewHerbst 🎉
Migration is very easy !

[MatthewHerbst]

Going to let v3 beta bake for the rest of the week. If all is well after that I'll promote this out of beta this coming weekend

[strarsis]

Awesome!

[drscottlobo]

Any progress on making these changes official?

[MatthewHerbst]

Ah, apologies, work has had me slammed and I haven't had time to look at this for a bit. I haven't had any more reports of issues with the beta so I will get it published as v3.0.0 before the weekend ends. Thanks for reminding me!

[drscottlobo]

Thank you!

[MatthewHerbst]

v3.0.0 has been published! Thanks everyone for your help and patience