angular-cli-ghpages is an Angular CLI builder and schematic that deploys Angular applications to GitHub Pages, Cloudflare Pages, or any Git repository. It wraps the gh-pages npm package and integrates with Angular CLI's deployment infrastructure via `ng deploy`. The tool features a modular architecture with separate entry points for standalone CLI usage, Angular builder integration, and schematic-based setup. It handles complex deployment concerns including build process integration, authentication token injection, CI environment metadata appending, and creation of necessary deployment files (.nojekyll, 404.html for SPA routing, CNAME for custom domains).
eslint-plugin-project-structure is a TypeScript-based ESLint plugin that enforces scalable, consistent project architecture through three configurable rules: folder-structure enforcement, file-composition constraints (e.g., `**/*.consts.ts` may only contain variables, `**/*.types.ts` only interfaces/types), and independent-modules enforcement to prevent massive dependency trees. The plugin parses all import syntaxes — ESM, CJS, dynamic `import()`, `require()`, `jest.mock()`, `jest.requireActual()`, plus `ExportAllDeclaration`/`ExportNamedDeclaration` — and validates file paths against micromatch glob patterns. Configuration is provided via JSON files validated against a bundled JSON schema, enabling IDE autocompletion and early error detection. The codebase is a standard ESLint plugin library: rules receive AST nodes and report violations, with utility modules handling import classification, cross-platform path resolution (Windows/POSIX), and multi-pattern glob matching. It is distributed as compiled CommonJS (`dist/index.js`) with a self-referencing dev dependency for integration testing. The project ships with comprehensive tests covering edge cases like Windows paths, `@types/` scoped packages, and external-import detection, plus CI running type checks, format checks, lint, and tests via Yarn 3.6.3.
Wails is a Go framework for building cross-platform desktop applications using web frontends (HTML/CSS/JS). It provides a CLI tool for project scaffolding, development server, and building. The architecture consists of a Go backend that communicates with an embedded WebView via a binding system that auto-generates TypeScript/JavaScript wrappers for Go services. It supports Windows (WebView2), macOS (WebKit), Linux (GTK/WebKit), and mobile (iOS/Android). Key entry points include `application.New()` in v3 and `wails.Run()` in v2. External dependencies include the WebView2 runtime on Windows, WebKitGTK on Linux, Cocoa on macOS, and various system libraries. The repository contains both v2 (legacy) and v3 (current) versions, with v3 introducing a new binding generator, built-in task runner (`wake`), improved service lifecycle, and cross-platform scaffolding.
FirebaseUI Web is a multi-package library that provides pre-built authentication UI components for web applications using Firebase Auth. It supports multiple frameworks (React, Angular, shadcn) with a shared core package that handles auth logic, state management, error handling, and internationalization. The library includes ready-to-use sign-in, sign-up, phone, email link, OAuth, and multi-factor authentication (SMS/TOTP) flows, all customizable via a composable behavior system. It is published as npm packages (@firebase-oss/ui-*) and includes extensive examples and end-to-end tests with Playwright against the Firebase Auth Emulator.
angular-oauth2-oidc is an Angular client library for OAuth 2.0 and OpenID Connect authentication in browser SPAs. Its core is OAuthService, a large stateful injectable that loads OIDC discovery documents, drives login via implicit flow, code flow + PKCE, or password flow, stores tokens through a pluggable OAuthStorage (default sessionStorage, with MemoryStorage fallback), validates tokens through pluggable ValidationHandler implementations, runs silent refresh/session checks via hidden iframes, and emits a typed event stream (OAuthEvent hierarchy) for lifecycle notifications. DefaultOAuthInterceptor attaches bearer tokens to outgoing HTTP calls against configured allowed URLs; UrlHelperService extracts tokens from redirect URLs for both hash and query strategies.
Tabby (formerly Terminus) is a cross-platform terminal emulator built with Electron and Angular 15. It serves as a modern replacement for terminal applications like Windows conhost, PowerShell ISE, PuTTY, macOS Terminal, and iTerm. The application provides integrated SSH, Telnet, and serial clients, local shell support (cmd, PowerShell, WSL, bash, etc.), split panes with drag-and-drop, a fully customizable hotkey system, themes, and an encrypted vault for credentials. The architecture is a monorepo of Angular modules (tabby-core, tabby-terminal, tabby-ssh, etc.) that communicate through dependency injection providers. A plugin system allows third-party packages to extend functionality via well-defined abstract classes (HotkeyProvider, ProfileProvider, TerminalDecorator, etc.). The web variant (tabby-web) provides a browser-based SSH/Telnet client but lags behind the desktop version. The codebase is mature with extensive i18n support, CI/CD pipelines, and community contributions, but shows some drift with Angular 15 being several versions behind current and some legacy naming (terminus- prefix).
NativeScript is a mature, cross-platform mobile application framework that enables developers to build native iOS, Android, and visionOS apps using JavaScript, TypeScript, or Angular. The repository is structured as a monorepo containing the core runtime (`@nativescript/core`) with platform-abstracted UI components, styling engine, data binding, and application lifecycle management; dual build toolchains (`@nativescript/vite` and `@nativescript/webpack5`) with Hot Module Replacement (HMR) support; platform type definitions (`@nativescript/types-ios`, `@nativescript/types-android`); and native widget libraries (Android Java, iOS Objective-C). The architecture is component-based: XML-declared UIs are parsed by a builder, instantiate native views, and styled via a custom CSS engine with selector matching, inheritance, and animations. An extensible property system with coercion, CSS properties, and change tracking drives reactivity. HMR infrastructure includes a Vite plugin that serves modules over WebSocket with framework-specific strategies (Angular, Vue, Solid, TypeScript). The codebase is heavily tested with unit tests (Vitest), platform-specific integration tests, and Appium E2E tests. Reusable design patterns include the observable data binding, property change origin tracking, platform-qualified file resolution, and CSS media query parsing. Notable technical drift risks include the coexistence of two build systems (webpack5 deprecated in favor of Vite), extensive platform-specific code duplication (`.android.ts`/`.ios.ts` pairs), and reliance on some deprecated iOS APIs in type declarations. Overall, it is a well-engineered framework with a large ecosystem and active development.
Ghostfolio is an open-source wealth management application that enables individuals to track and analyze their personal investment portfolios. It supports multiple asset classes (stocks, ETFs, cryptocurrencies, bonds, real estate) and integrates with numerous financial data providers (Yahoo Finance, CoinGecko, Alpha Vantage, etc.) to automatically fetch market prices, historical data, and asset profiles. The system provides comprehensive portfolio performance calculations (ROAI, TWR, MWR), benchmark comparisons, dividend tracking, and a rule-based X-ray analysis for risk assessment (currency/asset class/regional cluster risk, emergency fund coverage, fee ratios). It also includes a FIRE calculator, watchlist, and import/export functionality for activities. The architecture follows a full-stack monorepo pattern using Nx, with an Angular 22 frontend (standalone components, Material Design, Chart.js) and a NestJS 11 backend (Prisma ORM with PostgreSQL, Redis caching, Bull queues for background data gathering). Authentication supports JWT, OAuth (Google, OIDC), API keys, and WebAuthn passkeys. The system is self-hostable via Docker Compose and includes a premium subscription tier managed through Stripe. The codebase is modular with shared libraries (`libs/common` for DTOs, interfaces, utilities; `libs/ui` for reusable Angular components) and a clear separation of concerns across API modules, services, and queue processors. Key highlights include a pluggable data provider abstraction, an abstract portfolio calculator with caching and retry logic, a comprehensive permission and scope system for fine-grained access control, and a rich UI component library with Storybook documentation. The project is actively maintained with frequent releases, extensive Prisma migrations, and a large test suite for portfolio calculations and import validation. While the codebase shows some technical drift (proliferation of environment variables, deprecated endpoints, and multiple data provider integrations), the overall engineering quality is strong, with well-structured modules and reusable patterns that could be extracted for other financial applications.
The Alfresco Content Application (ACA) is a production-quality Angular single-page application serving as the reference frontend for Alfresco Content Services (ACS). It provides enterprise content management capabilities including file/folder browsing, search with saved searches and faceted filters, document preview and versioning, sharing, favorites, trash management, library management, and folder-based automation rules. The application is built as an Nx monorepo with multiple distributable libraries (aca-content, aca-shared, aca-playwright-shared) and follows an extension architecture that allows plugins to add custom actions, evaluators, routes, and sidebar panels. State management is handled by NgRx, and the UI leverages Angular Material and the Alfresco Development Framework (ADF). Extensive end-to-end tests are implemented using Playwright, with shared page objects and API wrappers for maintainability. The codebase is actively maintained with frequent releases and a well-defined version matrix tracking compatibility with ADF, ACS, Node, and Angular versions.
This repository is an educational documentation project, not a runtime application: index.js is a placeholder comment, and the only executable code is a ~70-file Vitest test suite whose purpose is to verify, line-by-line, the code examples embedded in ~60 MDX documentation pages. The docs cover 33 core JavaScript concepts plus a 'Beyond 33' extension of ~29 advanced topics (observer APIs, memory management, WeakMap/WeakSet, IndexedDB, etc.), rendered as a Mintlify site at 33jsconcepts.com. Each test file maps 1:1 to a concept page and references exact source line numbers in the .mdx files, making the tests executable documentation. GitHub Actions CI runs the suite on push/PR against Node LTS.
This repository is a collection of JavaScript interview questions and coding exercises, accompanied by a Node.js script for automatically generating a table of contents in the README. The core content consists of standalone JavaScript files that illustrate specific language concepts and patterns, such as closures, hoisting, event loop, and functional programming techniques. The repository includes several reusable utility implementations that demonstrate advanced JavaScript patterns. Notably, the debounce and throttle functions provide robust solutions for rate-limiting event handlers, while the deep merge function safely handles circular references during object merging using a WeakMap for tracking. These utilities are self-contained, have no internal dependencies, and can be easily extracted for use in other projects. The project is actively maintained, as evidenced by a recent commit (though the date appears to be in the future, indicating the most recent activity). It relies on a single external dependency (github-slugger) for generating anchor links, and the build process is automated via a GitHub workflow. While the majority of the content serves educational purposes, the highlighted components exhibit strong craftsmanship and adhere to modern JavaScript best practices.
This is a monorepo for SurveyJS, a comprehensive open-source form/survey library that renders dynamic JSON-based forms across multiple frontend frameworks (React, Angular, Vue 3, and plain JavaScript). The core engine (`survey-core`) handles model parsing, validation, expressions, triggers, input masks, drag-and-drop, theming, and localization. It provides 20+ question types (text, checkbox, radio, dropdown, matrix, ranking, file, signature, etc.) with extensible UI components via framework-specific rendering packages. The library also includes a built-in linter for survey JSON static analysis and a tester for programmatic survey test execution. Architecture follows a layered pattern: core logic separate from UI, with each framework package consuming the core via a shared set of exported model classes. The codebase is large (2896 files) but well-structured, featuring a custom expression parser (PEG), a modular action-bar system, advanced popup management with focus trapping, and a generic drag-drop engine. Maintenance is active with frequent releases, but there is some technical drift in the form of commented-out legacy testcafe tests, auto-generated theme files, and cross-framework duplication that requires careful synchronization.
This is a large, production-grade collaborative crafting companion for Final Fantasy XIV, consisting of an Angular web application (with SSR) and an Electron desktop client, plus a NestJS API and Firebase backend. The primary functionality includes crafting list management with tree-based ingredient breakdown, a full crafting rotation simulator, gearset planning with stat calculations and materia optimization, real-time gathering alarms based on Eorzea time and weather, marketboard price tracking via Universalis, inventory capture and optimization, fishing data and cooperative fishing train tool, commission board for player-to-player crafting services, free company workshop and airship/submarine management, island sanctuary workshop optimization, and a crowd-sourced data reporting system (Allagan Reports) for fish/hookset/bite times and desynthesis results. The codebase demonstrates advanced Angular/NgRx patterns, extensive use of RxJS for reactive data flows, a sophisticated lazy data loading system for game data extracted from the FFXIV client, and tight desktop integration via Electron IPC and packet capture. While there are some legacy patterns and a large feature surface that introduces maintenance complexity, the architecture is well-separated into libraries, the core data abstraction (LazyDataFacade, FirestoreRelationalStorage, base dialog components) is highly reusable, and the project remains actively developed with a large user and contributor community.
oidc-spa is a production-grade OpenID Connect (OIDC) client library designed for browser-first single-page applications. It implements the Authorization Code + PKCE flow with security-first defaults including in-memory token storage, DPoP (Demonstration of Proof-of-Possession) support, token substitution to prevent token leakage, and browser runtime freezing to resist monkey-patching attacks. The library provides framework-specific adapters for React, Angular, Next.js, Nuxt, TanStack Start, and React Router, each offering hooks, guards, and middleware for seamless authentication integration. It also includes a Vite plugin for build-time injection, a mock OIDC adapter for testing, and server-side utilities for access token validation (RFC 9068). The core is framework-agnostic, with a custom reactive event system (Evt) for state management and cross-tab synchronization via BroadcastChannel. The repository contains extensive example applications demonstrating login/logout, protected routes, role-based access, and auto-logout overlays across multiple frameworks.
This repository is the source code for the NG-NEST Angular UI component library (version 22.0.5), providing over 70 reusable components for building enterprise-grade web applications. The library includes a comprehensive set of UI elements such as buttons, tables, forms, dialogs, trees, date pickers, and more, all built with Angular's latest features including signals, standalone components, and OnPush change detection. The repository also contains a documentation/demo site that showcases each component with live examples in both English and Chinese, along with a full RBAC tutorial demonstrating a real-world admin panel using NestJS and Angular. The architecture follows a monorepo pattern: the library lives under `lib/ng-nest/ui/` with each component as an independent Angular module (with its own `ng-package.json`), while the documentation site resides in `src/` and uses the library itself. Key entry points include `lib/ng-nest/ui/index.ts` for the library and `src/app/app.config.ts` for the application. Data flows are primarily unidirectional via Angular signals and observables, with services like `XRepositoryAbstract` providing a consistent CRUD pattern for backend integration. External dependencies include Angular 22, Angular CDK, RxJS, and PrismJS for syntax highlighting. The library demonstrates strong engineering practices: consistent component property classes, a centralized portal service for overlays, a theme system with CSS variables and dark mode, and full internationalization support with 30+ locales. However, many component tests are disabled (using `xdescribe`), and there is some duplication in example data across language variants. Overall, it is a well-maintained, production-ready UI library with a high degree of reusability.
This is an Angular SDK library (`@auth0/auth0-angular`) that integrates Auth0 authentication (OAuth2/OIDC) into Angular single-page applications. It wraps the Promise-based `@auth0/auth0-spa-js` into Angular's reactive ecosystem using RxJS Observables, dependency injection, and Angular Router. The library provides core authentication flows (redirect/popup login, logout, token management), route protection via guards, automatic bearer token injection via HTTP interceptors, and additional features such as MFA, passkeys (WebAuthn), enterprise account linking, custom token exchange, and a MyAccount API client. It supports both traditional NgModule-based and modern standalone (functional) Angular patterns. The playground application included serves as a development and e2e test harness with a local OIDC provider. The architecture is clean, well-tested, and follows Angular best practices, though the core logic is delegated to the underlying Auth0 SPA SDK.
Onsen UI is a comprehensive mobile UI framework for building hybrid mobile apps and progressive web apps (PWAs) with native-like interfaces. The repository is a monorepo containing a core library built on Web Components, CSS components with iOS and Material Design theming, and official bindings for React, Vue 2, Vue 3, Angular 2+, and legacy AngularJS. The core defines custom HTML elements (e.g., `<ons-navigator>`, `<ons-tabbar>`, `<ons-dialog>`) that encapsulate mobile-specific UI patterns such as navigation stacks, tab bars, side menus, pull-to-refresh, lazy lists, and various form controls. The CSS component library provides a consistent, themable styling layer via CSS custom properties and BEM-like modifier classes. Framework bindings wrap these core elements for seamless integration with modern frontend frameworks. The repository also includes example applications, a CSS component previewer, and extensive documentation schemas. While the framework is mature and feature-rich, it shows signs of technical drift with deprecated APIs, multiple legacy binding packages, and a complex build infrastructure. It is actively maintained but appears to be in a stabilization phase rather than rapid development.
OVH CDS is an enterprise-grade continuous delivery and DevOps automation platform. The repository contains a set of Go services (API, CDN, hooks, VCS, repositories, hatcheries, worker, elasticsearch) managed via a common engine binary, supported by PostgreSQL, Redis, and OpenSearch/Elasticsearch, plus an Angular web UI, a cdsctl CLI, and gRPC-based action/integration plugins. In production it orchestrates pipelines and workflows, spawns workers on Kubernetes, Swarm, OpenStack, vSphere or local hosts, ingests VCS webhooks, stores job logs and artifacts through a pluggable CDN storage layer, and enforces fine-grained RBAC across projects, regions, workflows, and variable sets. Both legacy v1 workflows and newer as-code v2 workflows are implemented and actively maintained side-by-side.
Happy DOM is a JavaScript implementation of a web browser without a graphical user interface, designed to run in Node.js. It provides a comprehensive simulation of browser APIs including the DOM, HTML/SVG elements, CSSOM, Fetch, WebSocket, Canvas, Custom Elements, Shadow DOM, and more. The library is primarily used as a test environment for JavaScript frameworks (React, Vue, Angular, Lit, etc.) and supports server-side rendering via an optional server-renderer package. The codebase is a monorepo containing the core happy-dom package along with companion packages for global registration, Jest environment, server rendering, and a pluggable canvas adapter. It is actively maintained with thousands of tests and a large community. However, it exhibits moderate technical drift: some APIs are incomplete, there is significant boilerplate duplication across SVG/HTML element implementations, and a few deprecated settings linger. Overall, it is a solid, well-structured library but not exceptional in craftsmanship due to the repetitive patterns and some incomplete implementations.
This repository provides an Angular wrapper for the dragula drag-and-drop library. It exposes a directive (`[dragula]`) to mark containers as part of a drag group, and a singleton service (`DragulaService`) to configure groups and subscribe to typed RxJS observables for all dragula events. The library supports two-way model binding (`[(dragulaModel)]`) to synchronize dragged data with component arrays, and offers a plugin system for mock drake objects during testing. The architecture cleanly separates concerns: the directive handles DOM registration and model updates, while the service manages group lifecycle and event relay from native dragula callbacks to Angular Observables. It is built with Nx monorepo tooling and includes a demo application, e2e tests, and CI/CD pipelines for building, testing, and publishing to npm. The codebase demonstrates mature Angular patterns, including proper lifecycle management, subscription handling, and typed event emitters.