-
Notifications
You must be signed in to change notification settings - Fork 18
Headless ? #4
Comments
Thanks for opening this issue 👍 The short answer is no. This is something that I also need and I'm planning to do (but please feel free to send a PR if you end working on it!). I'm curious how you were planning on integrating with your CI. Any chance you could share your thoughts? In many CI services you have access to the git history and so with support for headless mode you could run |
Well I'd go with a KISS approach, package.json
😄 (Along with a |
That makes sense, thanks for sharing 👍 I believe there are some benefits in having this file under version control, but on the other hand as you mentioned there's the risk that the setup becomes too complicated. But either way being able to run |
Good to hear
|
I agree 👍 One nitpick regarding |
I am leaning towards not wanting a headless mode. I am thinking of a case where GA stops reporting data (For whatever reason), this goes unnoticed, and the generated browserslist is missing tons of browsers that very-much ought to be under support. I think having this tool be manually run and audited is important. |
Interesting feedback, thank you 👍 A month ago I started a prototype of a bot using GitHub Apps and a new permission that gives you write and read access to a single file in the repository the owner allows. I haven't worked on it since, but in case anyone is interested here's what I have so far: https://github.com/dmfrancisco/browserslist-ga-bot |
Is there a way to use, say, env variables to update the file in pure headless mode ?
This would allow hooking it in our CI pipeline, thus updating stats every push in the process
The text was updated successfully, but these errors were encountered: