Our vision is to build a service which provides everything they need to know about their dependency lifecycles and letting them make responsible decisions about upgrading to newer versions.
But, we are not there yet. Currently DepTrack helps you to get informed about the newer versions of your dependencies, and lets you build an updated package.json.
On the main page you have two options: you can start DepTrack by providing your package.json you want to update, or you can start DepTrack with a sample project, if you don’t have any project to test with.
Of course if you want to make a use of DepTrack, then you will start it your own project instead of a sample:
It is important to note that we never store your dependencies, project name or any other information found in your package.json. DepTrack can be used anonymously, without authentication, and with respect to your privacy. Simply put, you are safe.
How to upgrade to newer versions
When the app gets loaded, on the left side you can view & select newer versions of your npm dependencies found in your project. If you want to run through your modules and make a quick decision about upgrading the next major, minor or patch version of your dependency then you are at the right place. DepTrack gives it for you without complicating your life - this is our primary goal.
After you selected your desired dependency versions you can view your modified package.json with the updated version numbers by clicking the button.
You can copy-paste the resulting json directly into your project. All json properties which are not related to dependencies (like
"script" properties) will remain, since this json is an alteration of the original package.json, not a completely newly generated one.
Your project newsfeed
Have you ever wondered in what state your dependencies can be some time after you decided to use them? Are there any new features you may want to use? Are there any severe issues you may want to know about? Is it maintained at all?
When you pull your depencency into your project, you probably look around and figure out the current state of the repository. Signs of contribution activity like commit frequency, number of open pull requests, unanswered issues are factors which help you to make a decision about if you want to include the module in your project. But these factors change with time, and if you want to keep an eye on the dependency, you have to follow the modules’ lifecycles one by one, by watching them on GitHub or subscribing to their mailing lists (if they have any).
The DepTrack newsfeed is aimed to help you with this problem. The center-right pane is a project-specific GitHub event stream, which helps you to gather information about what is going on in your dependent projects. You can view it as your project-specific GitHub dashboard. It is supposed to give you an insight of happenings of your projects.
Our next plan is to build a better newsfeed, better serving its purpose by aggregating GitHub events in a more usable and consumable manner.
Our goal is to better separate events by the GitHub issue they belong to (if any). This way issue descriptions, comments, related pull requests and status changes will be grouped instead of appearing as separate, independent newsfeed entries. This means that we can present the events in a more informative way.
Stay tuned and leave a comment here if you want to share your thoughts with us. We plan to come back with new improvements shortly. In the meantime, subscribe to our newsletter or Follow @DepTrack on Twitter. See you soon!