argos-ci / argos-cli Goto Github PK

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

This package depends on update-notifier@^4.1.0, which, in turn, transitively depends on got@^9.6.0. The got package has a security vulnerability (see https://github.com/mui/material-ui/security/dependabot/72).
Updating update-notifier to the latest 6.0.2 does solve the dependency problem, but it also causes errors when running argos-cli. It's because v6.0.0` moved to pure ESM modules and doesn't work with CommonJS packages.
The fix would require transitioning argos-cli to ESM as well.

argos upload can upload too many image at the same time, creating timeout on server side.

Can we limit the number of images sent in one single query?

I tried to get started with Argos CI and got as far as the /<org>/<proj>/getting-started which landed me here. It is impossible to understand what will create the screenshots. There is just talk of uploading through the cli.

Usually something like this would require a server to generate the components on a separate page, which would then be processed by PhantomCSS or similar, etc. But this is highly project dependent stuff, and not something you touch upon at all in the material presented to the user. Which is why I have the growing suspicion that you might be able to take some shortcuts by scoping this down to some subsegment, like only projects relying on React where you can render PureComponents somehow.

Really, I have no idea ... which is a bit of an adoption stopper :-)