A CLI tool to generate Angular-based Chrome Extensions with support for all extension components.
@larscom/ng-chrome-extension is a CLI tool that generates Chrome Extension projects built with Angular. It simplifies the process of creating browser extensions by providing a pre-configured project structure that supports all Chrome Extension components like popups, options pages, and service workers. The tool handles the integration between Angular and Chrome's extension APIs, reducing setup time and complexity.
Angular developers who want to build Chrome Extensions without manually configuring the build process and extension structure. It's also suitable for teams needing a standardized way to create maintainable browser extensions.
Developers choose this tool because it offers a seamless Angular-first development experience for Chrome Extensions, with built-in support for all extension components and a streamlined workflow from development to production packaging. It eliminates the need to wire up Angular with Chrome Extension manifests and scripts manually.
CLI tool to generate angular chrome extensions
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports all major Chrome Extension components including popup, new tab, options page, side panel, service worker, and content scripts, as listed in the README's features.
Integrates Angular and TypeScript for building UI, providing a structured, maintainable codebase ideal for complex extensions, as emphasized in the philosophy.
Includes live reloading for most components and a dedicated dev server, enabling rapid iteration during development, as described in the 'How to use/develop' section.
Builds and packages the extension into a ZIP file ready for Chrome Web Store submission, simplifying the release process with npm run build:production.
Organizes each feature into standalone, lazily loaded Angular components, improving performance and code organization, as noted in the Angular folder description.
The README explicitly states the tool is not tested on Windows, making it unreliable for developers on that platform and limiting its reach.
Changes to content page and service worker scripts require manual extension reload in chrome://extensions, disrupting the development flow compared to other components.
Forces the use of Angular, which may not align with teams' existing tech stacks or preference for lighter, framework-agnostic approaches.