JARVIS CLI Tool

Prerequisite

The below commands were tested in Arch Linux

pip install virtualenv

if it’s not working properly try it with sudo.

git clone https://github.com/dyte-submissions/dyte-vit-2022-Avinash-Ashokar.git

cd dyte-vit-2022-Avinash-Ashokar/

virtualenv testing

source testing/bin/activate

python setup.py develop

jarvis configure ACCESS_TOKEN

In my case it is “jarvis configure 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”

My access token will be deleted by the time you are reading this 😅.

jarvis check -i input.csv axios@0.23.0 cors@2.8.5

The above command is to check versions. We could even check for multiple versions.

jarvis update -i input.csv axios@0.23.0 cors@2.8.6

The above command will create a pull request. We can create pull request for multiple files simultaneously.

Commands which can be used when we are stuck

You could run jarvis configure ACCESS_TOKEN command as many time as you want. Jarvis is smart enough when you try to execute check and update command without configuring

Even a extra functionality is added to check whether the given access token is correct

If we are stuck somewhere, then we can execute jarvis —help to know the available list of commands.
Both jarvis check and jarvis update command generate a packgeName.csv file, which can be used for later reference.
Jarvis get’s a bit annoyed when someone tests it with a package which is not present in the given repository links.

Thanks for this activity. It was fun.
And Hats off to the person who wrote that notion instruction. It was really creative. Please give them a hike.
I must finally thank stackoverflow, for helping me when I am stuck.