How ignacemaes/ember-phosphor-icons works
Main Components
– Holds the Template Registry (template-registry.ts) and the main TypeScript code that drives the component logic.
• Build and Tooling Infrastructure – Notice the “bin” folder with assembly scripts (e.g., assemble.ts), along with configuration files such as “pnpm-workspace.yaml”, “package.json”, and the various .github workflow files. These show CI/CD, packaging, and distribution pipelines.
• Test Application – The “test-app” directory acts as a sample Ember app that consumes the addon, providing integration tests and serving as a demonstration of usage.
Relationships and Interactions
• The test-app illustrates how an Ember application consumes the addon—showing how routing, application configuration, and tests exercise the addon components.
• CI/CD workflows in “.github/workflows” are set up to run tests, create releases, and distribute the addon, thereby integrating the development and deployment cycles.
Architectural Patterns and Design Principles
• Ember Addon (V2) Structure: The project follows Ember’s recommended addon format to facilitate integration with modern Ember (especially with Embroider).
• TypeScript and Glint Integration: Emphasizes type safety and IDE support for both code and templates.
Relevant Technologies and Frameworks
• Ember.js (v4.5+), Embroider, and ember-auto-import as essential runtime environments.
• TypeScript for static typing, with a particular focus on Glimmer components (using “.gts” files).
• Build tools and dependency management via pnpm (with “pnpm-lock.yaml” and “pnpm-workspace.yaml”).
• CI/CD pipelines configured through GitHub Actions (.github/workflows directory).