• Too many print statements are cluttering the output.
• Output is not clean. We need line breaks and separators.

Currently the config_maker.py forces the user to pick one of the existing package.json files if they choose to search for them.

We should also allow the user to pick an arbitrary folder after that operation.

look for updates in a git dependency

Can be implemented with: #11

which means that version is already published before.
...and do something with that information.
I am not sure yet.

Our way of handling config.json file is not friendly for project maintainers.

We should allow the project maintainers to execute the application on a specific folder. Then the program will search for a config.json file in that directory and act accordingly.

This will allow them to commit the config.json file to their own repositories and use the tool externally, targeting their project's config.json.

This might also be useful in the future if we decide to introduce support for multiple configs.

try running a subprocess

Allow the command to be run silently with parameters given.

Create a GUI for the whole application.

The whole codebase needs some refactoring.

Our way of handling paths are very fragile. We need to create Path objects from the get-go and use them instead of passing around strings.

This will require a re-write of the Config module.