https://github.com/morriq/microservices-webpack-plugin

Prevent loading scripts which are already loaded in another micro-app
https://github.com/morriq/microservices-webpack-plugin

chunk microservice microservices-webpack-plugin tailor webpack

Last synced: about 2 months ago
JSON representation

Prevent loading scripts which are already loaded in another micro-app

• Host: GitHub
• URL: https://github.com/morriq/microservices-webpack-plugin
• Owner: morriq
• Created: 2018-12-08T15:09:48.000Z (about 6 years ago)
• Default Branch: master
• Last Pushed: 2020-08-04T16:16:07.000Z (over 4 years ago)
• Last Synced: 2024-10-11T20:43:22.418Z (2 months ago)
• Topics: chunk, microservice, microservices-webpack-plugin, tailor, webpack
• Language: JavaScript
• Size: 608 KB
• Stars: 15
• Watchers: 2
• Forks: 1
• Open Issues: 4
• Metadata Files:
  • Readme: README.md
  • Changelog: CHANGELOG.md

Awesome Lists containing this project

README

        
# microservices-webpack-plugin

[![Greenkeeper badge](https://badges.greenkeeper.io/morriq/microservices-webpack-plugin.svg)](https://greenkeeper.io/)

This `plugin` solves problem with repeating packages from `node_modules` in microservices' chunks.

It uses [unpkg](https://unpkg.com) to load npm packages.

## Installation

`npm install -D microservices-webpack-plugin`

Let's try with `react`.

Modify your microservice's `webpack.config`:

- `output.libraryTarget` must be `amd`

- add to `plugins`

```

new MicroservicesWebpackPlugin({

  modules: [

    { name: 'react', path: `umd/react.production.min.js` },

  ]

})

```

## Scenario

You're using microservices with solutions such as [Tailor](https://github.com/zalando/tailor/).

You have many microservices which relays on the same version of `some node_modules dependency`.

You wonder how to don't load `some node_modules dependency` in every chunk.

## Problem

Tailor sends client application to browser via `headers` (more specifically via `Link`). And later it uses `require.js` to execute in browser.

It expects that `some node_modules dependency` is inside client application or was loaded earlier.

To solve that you could:

> add required libraries to tailor's template.

> create microservice which should gather common libraries into its chunk.

It's not the best approach because it makes invisible relation between microservices

- write in `some node_modules dependency` into `Header.Link`

Your chunk has required dependency `some node_modules dependency` and first of all it will try load `some node_modules dependency` from tailor's host

Inspiration [Webpack CDN Plugin](https://github.com/van-nguyen/webpack-cdn-plugin)