Plutt is a build tool that enables developers to generate microfrontends from framework-native components and to serve them version safely. The microfrontends are automatically safe to use in production if they work during development.
- Access transparency: Consuming applications use the microfrontends as regular components, without having to know that it is a microfrontend.
- Automatic Version Safety: At run-time Plutt will always upgrade to the latest version of a microfrontend, as long as it is non-breaking. This is done by supporting lock-step deployments.
- Framework Agnostic: Plutt applications can be consumed by any framework. Currently Plutt supports React and Vue, but it is easy to extend Plutt to support more frameworks.
- Type Safety: Microfrontends can be consumed with type safety. Any props that are used incorrectly can be found at compile-time.
$ npm install -g @digitalroute/plutt
$ plutt COMMAND
running command...
$ plutt (-v|--version|version)
@digitalroute/plutt/0.0.0-semantically-released darwin-x64 node-v13.10.1
$ plutt --help [COMMAND]
USAGE
$ plutt COMMAND
...All examples are located at Plutt Examples Collection.
Plutt is a build tool that enables developers to generate microfrontends from framework-native components and to serve them version safely. Plutt takes a framework-native component as input and outputs two types of artifacts: a Plutt Application (composed of the original Component and a Wrapper) and a Proxy. To serve Plutt applications, Plutt provides a Plutt Server.
You can use only a Plutt Application, but to get most benefits you should use the provided Proxy and Plutt Server.
A Plutt application is a self-contained microfrontend application that exposes functions for mounting with properties, updating the properties, and unmounting. Plutt applications are stored on a Plutt server and accessed in run-time, to ensure that the latest version is consumed.
A proxy is a framework-native component that knows how to fetch and mount a corresponding Plutt application. Plutt generates one proxy per supported framework, which currently is React and Vue. Proxies integrate into a parent application during compile-time. Proxies do not include any business logic, but they do include everything required to safely consume a Plutt application. Proxies fetch a specific version of a Plutt application which can be verified at compile-time to be non-breaking. If the Plutt application is typed, the proxy is also typed, and static analysis can be used to indicate if a Plutt application is integrated correctly.
Plutt applications are stored on a Plutt server, which is where dependents fetch Plutt applications from. Plutt server upgrade requests to Plutt applications so that dependents receive the latest non-breaking version. Semantic versioning is used to ensure that the upgraded version is non-breaking. This way, the team that provides a microfrontend is responsible for deciding when to update to production, while ensuring that updates do not break dependent applications. Dependent teams own the decision of when to upgrade breaking versions. Plutt server provides every team with the correct responsibilities that facilitate independent deployments.
Build a plutt app.
USAGE
$ plutt build
OPTIONS
-s, --sourceDirectory=sourceDirectory [default: src] Source directory for the plutt app.
-v, --verbose Prints extra information. Useful for debuging.
DESCRIPTION
Build a plutt app.
Make sure that there exists a src/ directory with an index.js.
display help for plutt
USAGE
$ plutt help [COMMAND]
ARGUMENTS
COMMAND command to show help for
OPTIONS
--all see all commands in CLI
See code: @oclif/plugin-help
Serve a plutt app.
USAGE
$ plutt serve [DIRECTORY]
ARGUMENTS
DIRECTORY [default: .] Directory to serve plutt apps from
OPTIONS
-p, --port=port [default: 5000] Port used to serve plutt app
This project is developed together with a thesis, that will finish this summer. A link to the thesis will be published here when the thesis is finished.