npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@cesarchamal/single-spa-home-app

v1.0.18

Published

AngularJS application with home page for be included in a single-spa application as registered app.

Downloads

48

Readme

single-spa-home-app

npm version

Part of Demo Microfrontends - A comprehensive Single-SPA microfrontend architecture demonstration

An AngularJS 1.x microfrontend for Single-SPA serving as the main landing page and demonstrating legacy framework integration strategies.

🏗️ Microfrontend Architecture

This application is one of 12 microfrontends in the demo-microfrontends project:

| Microfrontend | Framework | Port | Route | Repository | |---------------|-----------|------|-------|------------| | 🎯 Root App | Single-SPA | 8080 | Orchestrator | single-spa-root | | 🔐 Auth App | Vue.js | 4201 | /login | single-spa-auth-app | | 🎨 Layout App | Vue.js | 4202 | All routes | single-spa-layout-app | | 🏠 Home App | AngularJS | 4203 | / | This repo | | 🅰️ Angular App | Angular 8 | 4204 | /angular/* | single-spa-angular-app | | 💚 Vue App | Vue.js 2 | 4205 | /vue/* | single-spa-vue-app | | ⚛️ React App | React 16 | 4206 | /react/* | single-spa-react-app | | 🍦 Vanilla App | ES2020+ | 4207 | /vanilla/* | single-spa-vanilla-app | | 🧩 Web Components | Lit | 4208 | /webcomponents/* | single-spa-webcomponents-app | | 📘 TypeScript App | TypeScript | 4209 | /typescript/* | single-spa-typescript-app | | 💎 jQuery App | jQuery 3.6 | 4210 | /jquery/* | single-spa-jquery-app | | 🔥 Svelte App | Svelte 3 | 4211 | /svelte/* | single-spa-svelte-app |

Main Repository: demo-microfrontends

Features

  • AngularJS 1.8: Legacy Angular framework (1.x)
  • UI Router: Client-side routing with state management
  • Component Architecture: Modular component-based design
  • Legacy Integration: Shows migration path from AngularJS to modern frameworks
  • Home Dashboard: Landing page with application overview

Technology Stack

  • Framework: AngularJS 1.8.0
  • Router: Angular UI Router 1.0.25
  • Build Tool: Webpack 4 with custom configuration
  • Language: JavaScript (ES5+ compatible)
  • Integration: Single-SPA AngularJS adapter

Development

Prerequisites

  • Node.js (v18.0.0 or higher)
  • npm (v8.0.0 or higher)

Installation

npm install

Development Server

npm start
# Runs on http://localhost:4203

Build

npm run build
# Outputs to dist/single-spa-home-app.js

AngularJS Features

Component Architecture

// Home component definition
angular.module('home-app')
  .component('homeComponent', {
    template: homeTemplate,
    controller: HomeController,
    controllerAs: 'vm'
  });

UI Router Configuration

$stateProvider.state('home', {
  url: '/',
  template: '<home-component />',
});

$locationProvider.html5Mode({
  enabled: true,
  requireBase: false
});

Module System

  • Modular application structure
  • Dependency injection
  • Service layer architecture
  • Component lifecycle management

Single-SPA Integration

This microfrontend exports the required Single-SPA lifecycle functions:

export const bootstrap = ngLifecycles.bootstrap;
export const mount = ngLifecycles.mount;
export const unmount = ngLifecycles.unmount;

Mount Point

The application mounts to the DOM element with ID home-app:

<div id="home-app"></div>

Route Configuration

Configured to activate on the root route /:

singleSpa.registerApplication(
  'home',
  () => loadApp('single-spa-home-app'),
  showWhenAnyOf(['/'])
);

AngularJS Adapter Configuration

const ngLifecycles = singleSpaAngularJS({
  angular,
  domElementGetter: () => document.getElementById('home-app'),
  mainAngularModule: 'home-app',
  uiRouter: true,
  preserveGlobal: false,
  template: appTemplate
});

Legacy Framework Benefits

Migration Strategy

  • Gradual modernization approach
  • Coexistence with modern frameworks
  • Preserve existing functionality
  • Reduce migration risk

Team Familiarity

  • Existing AngularJS knowledge
  • Minimal learning curve
  • Proven patterns and practices
  • Established ecosystem

Incremental Updates

  • Component-by-component replacement
  • Maintain business continuity
  • Test-driven migration
  • Risk mitigation

Home Page Features

Dashboard Components

  • Application overview
  • Quick navigation links
  • Recent activity feed
  • System status indicators

User Interface

  • Responsive design
  • Bootstrap integration
  • Accessible components
  • Mobile-friendly layout

Data Integration

  • Service layer architecture
  • HTTP client integration
  • State management
  • Error handling

Component Structure

Home Component

function HomeController($scope, $http) {
  const vm = this;
  
  vm.$onInit = function() {
    // Component initialization
    vm.loadDashboardData();
  };
  
  vm.loadDashboardData = function() {
    // Load dashboard content
  };
}

Service Layer

angular.module('home-app')
  .service('HomeService', function($http) {
    this.getDashboardData = function() {
      return $http.get('/api/dashboard');
    };
  });

File Structure

single-spa-home-app/
├── src/
│   ├── components/           # AngularJS components
│   │   └── home.component.js # Main home component
│   ├── services/            # Application services
│   ├── app.module.js        # Main module definition
│   ├── routes.js            # UI Router configuration
│   ├── app.component.html   # Root template
│   └── singleSpaEntry.js    # Single-SPA integration
├── dist/                    # Build output directory
├── package.json             # Dependencies and scripts
├── webpack.config.js        # Webpack configuration
├── .gitignore              # Git ignore rules
└── README.md               # This file

Webpack Configuration

Library Build

module.exports = {
  entry: ['src/singleSpaEntry.js'],
  output: {
    library: 'single-spa-home-app',
    libraryTarget: 'umd',
    filename: 'single-spa-home-app.js'
  },
  plugins: [
    new webpack.optimize.LimitChunkCountPlugin({
      maxChunks: 1
    })
  ]
};

Module Rules

  • Babel transpilation for modern JavaScript
  • ESLint integration for code quality
  • HTML template loading
  • Source map generation

Legacy Integration Patterns

Dependency Management

  • Self-contained dependencies
  • No external requirements
  • Isolated module system
  • Clean separation of concerns

State Management

  • AngularJS services
  • Scope-based data binding
  • Event system integration
  • Cross-component communication

Performance Optimization

  • Lazy loading strategies
  • Efficient digest cycles
  • Memory leak prevention
  • Proper cleanup on unmount

Migration Considerations

Modernization Path

  1. Wrap in Single-SPA: Current state
  2. Component Isolation: Extract reusable parts
  3. Service Modernization: Update data layer
  4. Gradual Replacement: Replace with modern components
  5. Complete Migration: Remove AngularJS dependency

Compatibility

  • Works alongside modern frameworks
  • Shared routing integration
  • Common authentication
  • Consistent user experience

Performance

  • Bundle Size: ~300KB (including AngularJS)
  • Load Time: Fast with efficient bundling
  • Runtime: AngularJS digest cycle optimization
  • Memory: Proper cleanup and garbage collection

Browser Support

  • Modern browsers (ES5+)
  • IE9+ compatibility
  • Mobile browsers
  • Legacy system support

Testing

Unit Tests

npm run test:unit

E2E Tests

npm run test:e2e

Linting

npm run lint

Contributing

  1. Fork the repository
  2. Create a feature branch
  3. Follow AngularJS best practices
  4. Maintain backward compatibility
  5. Test migration scenarios
  6. Submit a pull request

License

MIT License - see LICENSE file for details.

Related Projects

🚀 Quick Start

Run the complete microfrontend system:

# Clone main repository
git clone https://github.com/cesarchamal/demo-microfrontends.git
cd demo-microfrontends

# Start all microfrontends
./run.sh local dev

Run this microfrontend individually:

npm install
npm start
# Visit http://localhost:4203

Author

Cesar Francisco Chavez Maldonado - AngularJS Legacy Integration Example