You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reopening this - I had to revert the "fix" in PR189. Status:
My first preference would be for the @react-pdf project to stop depending on buffer. From #2758 - according to this comment there was a prior fix in PR1891, but later changes re-introduced the dependency on buffer. I also found another ticket #3225 that has been open some months.
My second preference is to polyfill buffer. I am waiting for:
I know you mention everything runs as expected, but im getting increased cpu/ram usage to the point my fans kick in on my laptop because of the volume of console warnings.
I know you mention everything runs as expected, but im getting increased cpu/ram usage to the point my fans kick in on my laptop because of the volume of console warnings.
Hi @CraigIntuety - I think the best plan for the Buffer is not defined warning is if we add a manual polyfill, since vite-plugin-node-polyfills seems to be lagging a bit maintenance-wise when it comes to the upcoming Vite 8 release. To do that, I would probably look at upcoming Vite docs instructions in node polyfills. I'm not convinced this warning is related to performance, however. Generating the PDF the first time you load it happens in the dynamically in browser in a webworker, and make take some time/resources (probably depends on the size of the PDF you are generating, and the specs of your machine).
Going forward, this project has been acquired by Inkit - you can reach out to them directly if you need further support: https://www.inkit.com/contact-us.
Activity
#172 add vite buffer polyfill
#172 upgrade rolldown-vite
#172 simplify buffer polyfill
#172 workoround upstream issue in vite-plugin-node-polyfills with Vite 8
mtmacdonald commentedon Jan 15, 2026
Reopening this - I had to revert the "fix" in PR189. Status:
buffer. From #2758 - according to this comment there was a prior fix in PR1891, but later changes re-introduced the dependency onbuffer. I also found another ticket #3225 that has been open some months.buffer. I am waiting for:Buffer is undefinedeven when using this package (latest version, with latest Vite 8 beta)This task is blocked. But the app is functional (it concerns a runtime warning that does not impact using the app).
CraigIntuety commentedon Feb 9, 2026
I know you mention everything runs as expected, but im getting increased cpu/ram usage to the point my fans kick in on my laptop because of the volume of console warnings.
mtmacdonald commentedon Feb 17, 2026
Hi @CraigIntuety - I think the best plan for the
Buffer is not definedwarning is if we add a manual polyfill, sincevite-plugin-node-polyfillsseems to be lagging a bit maintenance-wise when it comes to the upcoming Vite 8 release. To do that, I would probably look at upcoming Vite docs instructions in node polyfills. I'm not convinced this warning is related to performance, however. Generating the PDF the first time you load it happens in the dynamically in browser in a webworker, and make take some time/resources (probably depends on the size of the PDF you are generating, and the specs of your machine).Going forward, this project has been acquired by Inkit - you can reach out to them directly if you need further support: https://www.inkit.com/contact-us.