Any JavaScript project requires 3rd party modules.
As soon as you depend on specific versions, your module falls behind.
I will show how to keep your software up to date without any effort (as long as there are some tests).
You can automatically upgrade dependencies for an individual project,
a collection of projects. You can even see the anonymous version upgrade results across the public projects around the world to judge if a particular update is likely to succeed. What about projects that depend on your software? Before releasing a new version, you can test some or all of your dependencies against the new code.
I hope that anyone trying to work around the problem of keeping the modules working together and being up to date will find my approach very useful.
speaker bio
Gleb Bahmutov is JavaScript ninja, image processing expert and software quality fanatic.
After receiving a PhD in computer science from Purdue University,
Gleb worked on laser scanners, 3D reconstruction, and panorama-based virtual tours at EveryScape.
Later Gleb switched to writing browser data visualization software at MathWorks.
After a year, Gleb went back to the startup environment and developed software quality
analysis tools at uTest (now Applause).
Today Gleb is developing real-time financial analysis tools at Kensho.
He blogs about software development topics at http://glebbahmutov.com/blog/
and links his projects at http://glebbahmutov.com/.
You can follow him and his work @bahmutov
Any JavaScript project requires 3rd party modules. As soon as you depend on specific versions, your module falls behind. I will show how to keep your software up to date without any effort (as long as there are some tests). You can automatically upgrade dependencies for an individual project, a collection of projects. You can even see the anonymous version upgrade results across the public projects around the world to judge if a particular update is likely to succeed. What about projects that depend on your software? Before releasing a new version, you can test some or all of your dependencies against the new code.
I hope that anyone trying to work around the problem of keeping the modules working together and being up to date will find my approach very useful.
speaker bio
Gleb Bahmutov is JavaScript ninja, image processing expert and software quality fanatic. After receiving a PhD in computer science from Purdue University, Gleb worked on laser scanners, 3D reconstruction, and panorama-based virtual tours at EveryScape. Later Gleb switched to writing browser data visualization software at MathWorks. After a year, Gleb went back to the startup environment and developed software quality analysis tools at uTest (now Applause). Today Gleb is developing real-time financial analysis tools at Kensho. He blogs about software development topics at http://glebbahmutov.com/blog/ and links his projects at http://glebbahmutov.com/. You can follow him and his work @bahmutov