Skip to content
When libraries go unmaintained episode artwork

EPISODE · Jun 26, 2019 · 1H

When libraries go unmaintained

from Frontend First · host EmberMap

Topics include: 2:44 – What to do if your app depends on an unmaintained addon 26:15 – The workflow of designers who are also coders 32:31 – Why the status quo of web tooling is insufficient for multi-app workflows 41:46 – Side effects in React and Ember, and how Hooks help authors avoid making API mistakes Links: Ember CLI Deprecation Workflow Adopted Ember Addons Matthew Beale's tweet on improving library APIs

Episode metadata supplied by the publisher feed · Published Jun 26, 2019

Embed this episode

Sam and Ryan talk about what to do when one of your application's dependencies becomes an unmaintained library. They also chat about how current tools for building and deploying web apps are underserving the modern multi-app workflow, as well as some lessons learned in API design from experimenting with React hooks.

Distinct summary based on available episode metadata or transcript content.

Ready to play

When libraries go unmaintained

0:00 1:00:31

No transcript for this episode yet

We transcribe on demand. Request one and we'll notify you when it's ready — usually under 10 minutes.

No similar episodes found.

No similar podcasts found.

Frequently Asked Questions

How long is this episode of Frontend First?

This episode is 1 hour and 0 minutes long.

When was this Frontend First episode published?

This episode was published on June 26, 2019.

Can I download this Frontend First episode?

Yes. Use the download control on the episode player to save the publisher-provided media file.
URL copied to clipboard!