Web Baseline Tiers Can Guide Teams to Drop Redundant JS Dependencies

Writing for Smashing Magazine on 7 August 2026, developer Jad Joubran argues that the web platform's Baseline availability tiers — Limited, Newly available, and Widely available — can serve as a practical audit framework for trimming JavaScript dependencies. His approach prompts teams to ask, for each library, whether the browser now natively handles the same task, whether the swap is safe for their specific user base, and whether the platform feature fully covers their use case. Joubran maps several common packages to potential native replacements, including timeago.js against Intl.RelativeTimeFormat, axios against fetch with AbortController, and tippy.js against the Popover API and anchor positioning. He notes that many of these libraries were installed for valid reasons but quietly outlived their purpose because dependency lists are rarely re-examined. The framework is intended to turn Baseline from a documentation badge into a recurring line item in quarterly dependency reviews, with the expectation that routine audits would also push framework starter templates to ship lighter defaults over time.