{"href":"https://api.simplecast.com/oembed?url=https%3A%2F%2Fwebrush.io%2Fepisodes%2Fepisode-184-why-so-hard-upgrading-your-dependencies-i9dweH_S","width":444,"version":"1.0","type":"rich","title":"Episode 184: Why so hard? Upgrading Your Dependencies.","thumbnail_width":300,"thumbnail_url":"https://image.simplecastcdn.com/images/b4af6a46-70c1-48ab-858e-ff4c06df0889/0d416bc6-ce3e-4e54-85f2-891934f5f287/back1.jpg","thumbnail_height":300,"provider_url":"https://simplecast.com","provider_name":"Simplecast","html":"<iframe src=\"https://player.simplecast.com/5399bf8f-006b-4b1d-9999-5b3bf79b55aa\" height=\"200\" width=\"100%\" title=\"Episode 184: Why so hard? Upgrading Your Dependencies.\" frameborder=\"0\" scrolling=\"no\"></iframe>","height":200,"description":"What does it mean to upgrade your dependancies? How do you deal with security issues or error messages when you do? What if you're the creator of an npm library - when do you issue upgrades? And should you built something yourself or use a third party version?"}