2e31e80e28
- Replace hand-rolled loading/error/empty markup with shared app-skeleton, app-empty-state, and app-button across catalog, product details, cart, compare, wishlist, and the public static-page renderer - Fix hardcoded hex colors that bypassed theme CSS variables (catalog, product details), restoring multi-tenant theme correctness - Remove ~1100 lines of dead "alt" cart theme CSS (never applied by the template) from cart.component.scss, bringing it back under the 40kB build budget (89.49kB -> 59.39kB cart-component chunk) - Swap legacy global .btn/.btn-ghost/.btn-primary classes for app-button in compare and wishlist empty/toolbar actions
Marketplace Frontend
Angular marketplace frontend for the client demonstration. The app uses standalone components, signals, runtime branding/configuration, and a production build optimized for the current marketplace experience.
Features
- Responsive marketplace storefront
- Category browsing and product detail pages
- Search and shopping cart flows
- Telegram login integration
- Payment handoff through the existing backend contract
- Runtime branding and configuration loading
- PWA manifest and service worker configuration
Development
Install dependencies:
npm install
Start the local development server:
npm start
Build for production:
npm run build
The production build is written to dist/dexarmarket/.
Project Structure
src/
├── app/
│ ├── components/ # Shared storefront components
│ ├── core/ # Runtime, config, guards, providers, interceptors
│ ├── dynamic-renderer/ # Page, section, and widget rendering pipeline
│ ├── facades/ # Runtime, website, builder, and backoffice facades
│ ├── pages/ # Storefront, info, legal, cart, search, and item pages
│ ├── services/ # API, cart, auth, SEO, Telegram, and language services
│ └── widgets/ # Dynamic renderer widgets
├── assets/mock/ # Local mock configuration and catalog data
├── environments/ # Development and production environment settings
└── styles/ # Shared global styles and themes
Useful Checks
npm run build
npm run arch:check
Notes
- Authentication and payment integrations are intentionally left on their existing contracts.
- Renderer and runtime architecture should remain stable during demo preparation.
- Client-facing content should avoid placeholder names, mock labels, and temporary routes.