TechPrufer
Get started
GitHub
GitHub logoGitHub · Feature trail

Frontend JavaScript Dependency Management

2 posts · Sep 2018 – Sep 2026

What this trail covers

This feature thread tracks the evolution of managing JavaScript dependencies in frontend development, focusing on reducing reliance on external libraries and adopting modern web standards. It covers the journey from early adoption of libraries like jQuery to a complete decoupling, leveraging native browser APIs and Web Components for a leaner, more performant, and maintainable frontend. The thread also encompasses strategies for incremental migration, automated code quality enforcement, and the adoption of CSS Modules to replace CSS-in-JS solutions, significantly improving server-side rendering performance and component initialization times.

All GitHub trails
  1. Improving site performance by shipping more CSSThis post details the migration of GitHub's frontend styling from CSS-in-JS solutions (like styled-components and the `sx` prop) to CSS Modules. It outlines a phased approach: first migrating the Primer Design System components, then systematically reducing `sx` prop usage across the codebase, and finally decoupling theming logic. The post highlights the performance gains achieved, including a 55% reduction in server-side render time and a 25% reduction in component initialization time, and details the use of feature flags, visual regression tests, and automated tooling (VS Code plugins, codemods) for a safe and gradual migration. It also notes the eventual removal of `styled-components` and `styled-system` dependencies.
  2. Removing jQuery from GitHub.com frontendThis post details the successful removal of jQuery as a frontend dependency on GitHub.com. It explains the historical context of jQuery's adoption, the technical reasons for its deprecation (e.g., availability of standard browser APIs like querySelectorAll, Element.classList, Fetch API, addEventListener), and the challenges and strategies involved in its incremental decoupling. Key strategies include discouraging new jQuery usage via ESLint, maintaining custom jQuery builds to remove unused modules, dropping support for older browsers, and converting legacy behaviors to vanilla JavaScript and Custom Elements. The post also highlights the benefits of this migration, such as reduced bundle size, faster page load times, and improved code maintainability.