Module Federation with Angular: Sharing service from Shell to Remote

 For the project setup refer: app

Let's say i have shell and remote right now
With Module federation installed
And Also angular.json updated 

shellserv.service.ts

import {Injectable} from '@angular/core';

@Injectable({
  providedIn: 'root' // Ensure the service is available globally
})
export class ShellService {
  constructor() {
  }

  sayHello() {
      return "hello from Shell!!"
  }
}

Make sure this works in shell app first

import { ApplicationConfig, provideZoneChangeDetection } from '@angular/core';
import { provideRouter } from '@angular/router';

import { routes } from './app.routes';
import {ShellService} from './shellserv.service';

export const appConfig: ApplicationConfig = {
  providers: [
provideZoneChangeDetection({ eventCoalescing: true }), 
provideRouter(routes), 
ShellService]
};
import { Component } from '@angular/core';
import { RouterOutlet } from '@angular/router';
import {ShellService} from './shellserv.service';

@Component({
  selector: 'app-root',
  imports: [RouterOutlet],
  providers: [ShellService],
  templateUrl: './app.component.html',
  styleUrl: './app.component.scss'
})
export class AppComponent {
  constructor(private serv: ShellService) {
  }
  title = 'shell';

  ngOnInit() {
    console.log(this.serv.sayHello())
  }
}

If its fine, add the 'exposes' object in the webpack

shell/webpack.config.ts

const { shareAll, withModuleFederationPlugin } = require('@angular-architects/module-federation/webpack');

module.exports = withModuleFederationPlugin({

  name: 'shell',
  filename: 'remoteEntry.js',
  exposes: {
    './SharedService': './src/app/shellserv.service.ts'
  },
  shared: {
    ...shareAll({ singleton: true, strictVersion: true, requiredVersion: 'auto' }),
  }
});

REMOTE

remote/webpack.config.ts

const { shareAll, withModuleFederationPlugin } = require('@angular-architects/module-federation/webpack');

module.exports = withModuleFederationPlugin({

  name: 'remote',
  filename: 'remoteEntry.js',
  exposes: {
    './Component': './src/app/app.component.ts',
  },
  remotes: {
    shell: 'shell@http://localhost:4200/remoteEntry.js'
  },
  shared: {
    ...shareAll({ singleton: true, strictVersion: true, requiredVersion: 'auto' }),
  },

});

remote/app.component.ts

import { loadRemoteModule } from '@angular-architects/module-federation';
import { Component } from '@angular/core';
import { RouterOutlet } from '@angular/router';

@Component({
  selector: 'app-root',
  imports: [RouterOutlet],
  templateUrl: './app.component.html',
  styleUrl: './app.component.scss'
})
export class AppComponent {
  title = 'remote';
  message?: string;
  constructor() {
    this.loadShellService()
  }

  async loadShellService() {
    try {
      const module = await loadRemoteModule({
        remoteEntry: 'http://localhost:4200/remoteEntry.js',
        type: 'module',
        exposedModule: './SharedService'
      });

      const test = new module.ShellService();
      this.message = test.sayHello()

      console.log('SharedService Module Loaded:', module);
    } catch (error) {
      console.error('Error loading SharedService:', error); // Log the actual error
    }
  }

}

Just to note, this is the router i have (unrelated, just putting it here)

import { loadRemoteModule } from '@angular-architects/module-federation';
import { Routes } from '@angular/router';

export const routes: Routes = [
  {
    path: 'remote',
    loadComponent: () =>
      loadRemoteModule({
        type: 'module',
        remoteEntry: 'http://localhost:4201/remoteEntry.js',
        exposedModule: './Component'
      }).then(m => m.AppComponent)
  },
];

remote/app.component.html


<h1>hey from remote {{message}}</h1>

<router-outlet />




Comments

Post a Comment

Popular posts from this blog

Inside the JavaScript Memory Box: Visualizing Variables, References, and Copies

Image
There is a difference in the way JavaScript refences variables based on whether they are primitive or non-primitive Primitive Types: string, number, bigint, Boolean, symbol, null, undefined Non-Primitive: Arrays, Objects Each variable in JS is stored in a memory “box” Assignments: But when another variable tries to assign this value, JS thinks “wait, is this a primitive or non-primitive? Because if it is primitive, I will create a new box for this new variable with the same content. But if it’s not, I will just create a refence to the existing box” PRIMITIVE: Analogy: Let's say you have a note that says 5. You give a copy of this note to your friend.  Friend now updates this copy to 10. But your copy still says 5 let a = 5; let b = a; b = 10; //a remains unchanged NON-PRIMITIVE: Analogy: Let's say you have a note with address "123 Elm Street". In that house lives a cat named "Tom". You give a copy of this note to your friend. Friend now goes t...
Read more

React & State Management: All Concepts

Section 1: Fundamentals 1. Counter with increment, decrement, reset — useState Remember: prev is needed when the new state depends on the old state. When you're setting a hardcoded value like 0, you just pass 0 directly. Why:  reason prev matters — if multiple state updates happen in the same render cycle, React batches them. Using prev guarantees you're working off the latest state, not a stale snapshot. 2. Toggle show/hide paragraph — useState Remember: onClick={toggle} — pass the function reference, not the call. onClick={() => toggle()} — also fine, arrow function that calls toggle when clicked. onClick={toggle()} — calls toggle immediately during render, setVisible triggers re-render, toggle calls again, infinite loop. Why: JSX evaluates expressions inside {} during render. toggle() is an expression that executes immediately. React doesn't get a chance to attach it as a handler — it just runs it right there, state updates, component re-renders, runs again. ...
Read more

React: Communication between components

Parent to Child: Props Child to Parent Callback Props (advanced props) Controlled Components useImperative hook  Nested Tree: useContext Sibling: Lift State Up PARENT TO CHILD: Props App.jsx Users.jsx <User name ={user} /> function User({ name }) {  return <h1> {name} </h1> } CHILD TO PARENT a) Callback Props (Advanced Props) Parent.jsx Child1.jsx export function Parent() {   function sayHello () {     alert(“hello triggered”)   }   <Child1 onSayHello ={ sayHello } /> } function Child1({ onSayHello }) {   return <button onClick={ onSayhello() }>          Click       </button> } b) Controlled Components Usually used in forms. Controlled components mean the parent owns the state, the child renders inputs, and every ch...
Read more