This PR updates examples in `.md` files (both docs and blog posts) to use positional args. Nx 20 changes the position arg to be either `directory` for apps/libs or `path` for artifacts (e.g. components). So before you'd do this: ``` nx g app myapp --directory=apps/myapp nx g lib mylib --directory=libs/mylib nx g lib mylib --directory=libs/nested/mylib nx g lib @acme/foo --directory=libs/@acme/foo --importPath=@acme/foo nx g component foo --directory=libs/ui/src/foo --pascalCaseFiles ``` Will now be simplified to ``` nx g app apps/myapp nx g lib libs/mylib nx g lib libs/nested/mylib nx g lib libs/@acme/foo # name and import path are both "@acme/foo" nx g component libs/ui/src/foo/Foo ``` For cases where `name` and `importPath` need to be changed, you can always manually specify them. ``` nx g lib libs/nested/foo # name is foo nx g lib libs/nested/foo --name=nested-foo # specify name with prefix nx g lib libs/@acme/foo --name # use "foo" as name and don't match importPath nx g lib libs/@internal/foo --importPath=@acme/foo # different importPath from name <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior <!-- This is the behavior we have today --> ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #
165 lines
4.7 KiB
Markdown
165 lines
4.7 KiB
Markdown
# Federate a Module
|
|
|
|
Module Federation is a concept that allows developers to share code between applications at run-time. It is a way of doing micro-frontends, but it can also be used to share code between applications that are not micro-frontends.
|
|
|
|
In the context of Module Federation, a _module_ can be thought as any piece of code, functionally independent, that can be reused in different applications. It can be a component, a service, a library, a utility, etc.
|
|
|
|
In order to share a module, it must be _federated_. This means that the module must be configured to be shared, and the application that wants to use it must be configured to use it.
|
|
|
|
**Nx** includes first class support for Module Federation for React and Angular applications. This means that you can federate modules in your workspace with a few simple commands.
|
|
|
|
{% callout type="info" title="Assumption" %}
|
|
With this recipe we assume that you have already created a workspace with at least one React or Angular Module Federation host application.
|
|
If you haven't, you can follow the [Create a Host Recipe](/recipes/module-federation/create-a-host).
|
|
{% /callout %}
|
|
|
|
## Step 1: Create the module
|
|
|
|
We will create a module that exports a hello function.
|
|
Since we are using Nx, we will create a library for this module.
|
|
|
|
**Create a library**
|
|
|
|
```shell
|
|
nx generate @nx/js:library hello --unitTestRunner=jest --projectNameAndRootFormat=as-provided
|
|
```
|
|
|
|
Update the `hello.ts` file with the following code:
|
|
|
|
```typescript {% fileName="hello/src/lib/hello.ts" %}
|
|
export default function hello(): string {
|
|
return 'Hello from Nx';
|
|
}
|
|
```
|
|
|
|
Update `hello/` barrel file `index.ts` with the following code:
|
|
|
|
```typescript {% fileName="hello/src/index.ts" %}
|
|
export { default } from './lib/hello';
|
|
```
|
|
|
|
## Step 2: Federate the module
|
|
|
|
Now that we have created the module, we need to configure it to be federated.
|
|
|
|
{% tabs %}
|
|
{%tab label="React"%}
|
|
|
|
```shell
|
|
nx generate @nx/react:federate-module hello/src/index.ts --name=hello --remote=greeting --projectNameAndRootFormat=as-provided
|
|
```
|
|
|
|
{% /tab %}
|
|
{%tab label="Angular"%}
|
|
|
|
```shell
|
|
nx generate @nx/angular:federate-module hello/src/index.ts --name=hello --remote=greeting --projectNameAndRootFormat=as-provided
|
|
```
|
|
|
|
{% /tab %}
|
|
{% /tabs %}
|
|
|
|
{% callout type="note" title="Remote does not exist" %}
|
|
If the remote provided does not exist (in this instance _greeting_), Nx will create it for you.
|
|
{% /callout %}
|
|
|
|
This command will:
|
|
|
|
- Adds a module entry to the `greeting` remote module federation config file.
|
|
|
|
{% tabs %}
|
|
{%tab label="Typescript Config File"%}
|
|
|
|
```typescript {% fileName="greeting/module-federation.config.ts" %}
|
|
import { ModuleFederationConfig } from '@nx/webpack';
|
|
|
|
const config: ModuleFederationConfig = {
|
|
name: 'greeting',
|
|
exposes: {
|
|
'./Module': './src/remote-entry.ts',
|
|
'./Hello': 'hello/src/index.ts', // <-- this line was added,
|
|
},
|
|
};
|
|
export default config;
|
|
```
|
|
|
|
{% /tab %}
|
|
{%tab label="Javascript Config File"%}
|
|
|
|
```javascript {% fileName="greeting/module-federation.config.js" %}
|
|
module.exports = {
|
|
name: 'greeting',
|
|
exposes: {
|
|
'./Module': './src/remote-entry.ts',
|
|
'./Hello': 'hello/src/index.ts', // <-- this line was added
|
|
},
|
|
};
|
|
```
|
|
|
|
{% /tab %}
|
|
{% /tabs %}
|
|
|
|
- Adds a Typescript path mapping to the `greeting/Hello` module in your root TSConfig file.
|
|
|
|
```json {% fileName="/tsconfig.base.json" %}
|
|
{
|
|
"paths": {
|
|
"greeting/Module": ["greeting/src/remote-entry.ts"],
|
|
"greeting/Hello": ["hello/src/index.ts"] // <-- this line was added
|
|
}
|
|
}
|
|
```
|
|
|
|
## Step 3: Use the module
|
|
|
|
Update the host application to use the federated module.
|
|
|
|
{% tabs %}
|
|
{%tab label="Typescript Config File"%}
|
|
|
|
```ts {% fileName="host/module-federation.config.ts" %}
|
|
import { ModuleFederationConfig } from '@nx/webpack';
|
|
|
|
const config: ModuleFederationConfig = {
|
|
name: 'host',
|
|
remotes: ['greeting'], // <-- Ensure that greeting remote is listed here
|
|
};
|
|
|
|
export default config;
|
|
```
|
|
|
|
{% /tab %}
|
|
{%tab label="Javascript Config File"%}
|
|
|
|
```javascript {% fileName="host/module-federation.config.js" %}
|
|
module.exports = {
|
|
name: 'host',
|
|
remotes: ['greeting'], // <-- Ensure that greeting remote is listed here
|
|
};
|
|
```
|
|
|
|
{% /tab %}
|
|
{% /tabs %}
|
|
|
|
```tsx {% fileName="host/src/app/app.tsx" %}
|
|
import hello from 'greeting/Hello';
|
|
|
|
export function App() {
|
|
return <div>{hello()}</div>;
|
|
}
|
|
|
|
export default App;
|
|
```
|
|
|
|
If you are using Angular, you would update the application in a similar fashion to use the federated module.
|
|
|
|
## Step 4: Run the application
|
|
|
|
Just run the application as usual.
|
|
|
|
```shell
|
|
nx serve host
|
|
```
|
|
|
|
To start the application, use the following address: [http://localhost:4200](http://localhost:4200). Once opened, you'll see the message **"Hello from Nx"**. This message is loaded from the greeting remote, which runs on port 4201.
|