-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Split packet so npm users don't need to install pupeteer on pure browser installation #115
Comments
Thanks for the feedback...looking in to this |
Hi again @napalu, Thanks in advance |
Hi @hbi99 I was thinking it could be split in 2 packages.
It would mean maintaining two separate package builds. I'll try to see if there's an easier way but right now nothing comes to mind. |
Hi @napalu, Meanwhile, can you give me a gist of your npm commands, when installing packages for browser environment? Thanks in advance |
Since, I am not getting feedback on this issue, I am closing it. Re-open it if you want to pursue this issue. |
I'm stuck with the same issue as OP. Do we have any solution yet? |
Any solution on this? I wanted to implement this on React but I seem to encounter issues with Puppeteer being unable to run on a React app. Hope this issue gets reopened. |
I removed puppetter support in v2.2.8 |
Would be nice for those of us using npm as a package manager for our browser-based development to have an npm package which does not pull puppeteer on install.
The text was updated successfully, but these errors were encountered: