wiredep
Automatically injects Bower package dependencies into your HTML, Jade, Sass, and other source files.
What is wiredep?
Wiredep is a Node.js tool that automatically injects Bower package dependencies into your source code files. It reads your project's bower.json and dependency chain, then injects the correct script and link tags into placeholders in your HTML, Jade, Sass, and other files, ensuring proper load order.
Front-end developers and build engineers using Bower for package management who want to automate the injection of dependencies into their source files as part of their build process.
Developers choose Wiredep because it eliminates the manual task of updating script tags when adding or updating Bower packages, integrates smoothly with popular build tools like Gulp and Grunt, and supports multiple file formats with extensive configuration options.
Overview
Wire Bower dependencies to your source code.
Use Cases
Best For
- Automatically injecting Bower dependencies into HTML files
- Integrating Bower with Gulp or Grunt build processes
- Managing front-end library dependencies in Jade or Pug templates
- Injecting CSS and JS from Bower packages into Sass or Less projects
- Ensuring correct load order for Bower dependencies
- Overriding Bower package main entries for non-standard packages
Not Ideal For
- Projects using modern package managers like npm or Yarn instead of Bower
- Applications built with module bundlers such as Webpack or Vite that handle dependencies through ES6 imports
- Teams requiring dynamic dependency loading or server-side rendering with conditional asset injection
Pros & Cons
Pros
Reads Bower's dependency graph to inject scripts and styles in the correct load order, preventing manual errors as highlighted in the README's dependency resolution feature.
Out-of-the-box support for HTML, Jade, Sass, Less, and other file types, with extensible configuration for custom formats, as shown in the fileTypes section.
Seamlessly integrates with Gulp via streams and has a dedicated Grunt plugin, making it easy to incorporate into common build workflows, with examples provided.
Offers an API to retrieve dependency paths without file modification, enabling custom build logic, as demonstrated in the programmatic access section.
Allows overriding Bower package properties like main files, handling non-standard packages through project configuration or inline overrides, as detailed in the Bower Overrides part.
Cons
Bower is no longer actively maintained, making Wiredep a legacy tool with limited future support and relevance in modern ecosystems, as implied by its reliance on Bower.
Frequently encounters Bower packages with missing or incorrect main/dependency fields, requiring manual fixes or verbose overrides, which the README admits as a common problem.
Only injects static tags into source files, unsuitable for modern applications with dynamic module loading, code splitting, or server-side rendering, as it lacks dynamic handling capabilities.
The command-line interface was split into a separate module (wiredep-cli), adding extra installation steps and potential confusion, as noted in the README's CLI section.
Frequently Asked Questions
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.