-
Notifications
You must be signed in to change notification settings - Fork 30
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
Client-side support #9
Comments
I guess some dependencies of this project require Node. But this repo needs a huge list of browsers to work, I would be worried about the size of the file Maybe what you are looking for is something like a feature detection package |
Feature detection is great but our use-case is to just inform customers that we didn't test our product in their browser yet |
this project is not thinked to be executed client side so I wouldn't be supprise if it fails. if your files-server is built in Node (with express for example), you can run this project server side for choosing different html template based on the browser user's agent |
Including browserlist-useragent in the webpack's bundle adds 400kb gzipped and almost 3mb unzipped. It is definitely not thinked to be executed client side. |
This is a issue in an dependency - |
I think ideal solution would be to have the browsers list generated on build time from the actual It's not directly related to |
FYI: |
Hi! I have a problem with running your lib on client side. I need to detect if current browser is supported or not and notify the user if not.
I've tried to compile it with webpack but one of it's dependencies uses native node.js modules (to be more specific it's
useragent
) and it either not compile or takes a lot of unnecessary code to the bundle. Do you have any workaround how to use your lib in browser? Maybe I'm doing something wrong.Thanks.
The text was updated successfully, but these errors were encountered: