Skip to main content

@podium/podlet

Module for building page fragment servers for micro frontend architectures.

A podlet server is responsible for generating HTML fragments which can then be used in a @podium/layout server to compose a full HTML page.

This module can be used together with a plain Node.js HTTP server or any HTTP framework and any templating language of your choosing (or none if you prefer).

Connect compatible middleware based frameworks (such as Express) are considered first class in Podium and so this module provides a .middleware() method for convenience.

For writing podlet servers with other HTTP frameworks, please see the HTTP Framework Compabillity section.

Installation

$ npm install @podium/podlet

Getting started

Building a simple podlet server.

import express from 'express';
import Podlet from '@podium/podlet';

const app = express();

const podlet = new Podlet({
name: 'myPodlet',
version: '1.0.0',
pathname: '/',
development: true,
});

app.use(podlet.middleware());

app.get(podlet.content(), (req, res) => {
if (res.locals.podium.context.locale === 'nb-NO') {
return res.status(200).podiumSend('<h2>Hei verden</h2>');
}
res.status(200).podiumSend(`<h2>Hello world</h2>`);
});

app.get(podlet.manifest(), (req, res) => {
res.status(200).send(podlet);
});

app.listen(7100);

Constructor

Create a new Podlet instance.

const podlet = new Podlet(options);

options

optiontypedefaultrequireddetails
namestringnullName that the Podlet identifies itself by
pathnamestringnullPathname of where a Podlet is mounted in an HTTP server
versionstringnullThe current version of the podlet
manifeststring/manifest.jsonDefines the pathname for the manifest of the podlet
contentstring/Defines the pathname for the content of the podlet
fallbackstringnullDefines the pathname for the fallback of the podlet
loggerobjectnullA logger which conforms to a log4j interface
developmentbooleanfalseTurns development mode on or off
name

The name that the podlet identifies itself by. This is used internally for things like metrics but can also be used by a layout server.

This value must be in camelCase.

Example:

const podlet = new Podlet({
name: 'myPodlet';
});
pathname

Pathname for where a podlet is mounted in an HTTP server. It is important that this value matches where the entry point of a route is in an HTTP server since this value is used to define where the manifest is for the podlet.

If the podlet is mounted at the "root", set pathname to /:

const app = express();
const podlet = new Podlet({
name: 'myPodlet',
version: '1.0.0',
pathname: '/',
});

app.use(podlet.middleware());

app.get('/', (req, res, next) => {
[ ... ]
});

If the podlet is to be mounted at /foo, set the pathname to /foo and mount middleware and routes at or under /foo

const app = express();
const podlet = new Podlet({
name: 'myPodlet',
version: '1.0.0',
pathname: '/foo',
});

app.use('/foo', podlet.middleware());

app.get('/foo', (req, res, next) => {
[ ... ]
});

app.get('/foo/:id', (req, res, next) => {
[ ... ]
});
version

The current version of the podlet. It is important that this value be updated when a new version of the podlet is deployed since the page (layout) that the podlet is displayed in uses this value to know whether to refresh the podlet's manifest and fallback content or not.

Example:

const podlet = new Podlet({
version: '1.1.0';
});
manifest

Defines the pathname for the manifest of the podlet. Defaults to /manifest.json.

The value should be relative to the value set on the pathname argument. In other words if a podlet is mounted into an HTTP server at /foo and the manifest is at /foo/component.json, set the pathname and manifest as follows:

const app = express();
const podlet = new Podlet({
name: 'myPodlet',
version: '1.0.0',
pathname: '/foo',
manifest: '/component.json',
});

app.get('/foo/component.json', (req, res, next) => {
res.status(200).json(podlet);
});

The .manifest() method can be used to retrieve the value after it has been set.

content

Defines the pathname for the content of the Podlet. The value can be a relative or absolute URL. Defaults to /.

If the value is relative, the value should be relative to the value set using the pathname argument. For example, if a podlet is mounted into an HTTP server at /foo and the content is served at /foo/index.html, set pathname and content as follows:

const app = express();
const podlet = new Podlet({
name: 'myPodlet',
version: '1.0.0',
pathname: '/foo',
content: '/index.html',
});

app.get('/foo/index.html', (req, res, next) => {
[ ... ]
});

The .content() method can be used to retrieve the value after it has been set.

fallback

Defines the pathname for the fallback of the Podlet. The value can be a relative or absolute URL. Defaults to an empty string.

If the value is relative, the value should be relative to the value set with the pathname argument. If a podlet is mounted into an HTTP server at /foo and the fallback is at /foo/fallback.html, set pathname and fallback as follows:

const app = express();
const podlet = new Podlet({
name: 'myPodlet',
version: '1.0.0',
pathname: '/foo',
fallback: '/fallback.html',
});

app.get('/foo/fallback.html', (req, res, next) => {
[ ... ]
});

The .fallback() method can be used to retrieve the value after it has been set.

logger

Any log4j compatible logger can be passed in and will be used for logging. Console is also supported for easy test / development.

const podlet = new Podlet({
logger: console;
});

Under the hood abslog is used to abstract out logging. Please see abslog for further details.

development

Turns development mode on or off. See the section about development mode.

Podlet Instance

The podlet instance has the following API:

.middleware()

A Connect/Express compatible middleware function which takes care of the multiple operations needed for a podlet to operate correctly. This function is more or less a wrapper for the .process() method.

Important: This middleware must be mounted before defining any routes.

const app = express();
app.use(podlet.middleware());

The middleware will create an HttpIncoming object and store it at res.locals.podium.

Returns an Array of internal middleware that performs the tasks described above.

.manifest(options)

This method returns the value of the manifest argument that has been set in the constructor.

Set the manifest using the default pathname which is /manifest.json:

const app = express();
const podlet = new Podlet({
name: 'myPodlet',
version: '1.0.0',
pathname: '/',
});

app.get(podlet.manifest(), (req, res, next) => {
res.status(200).json(podlet);
});

Set the manifest to /component.json using the manifest argument on the constructor:

const app = express();
const podlet = new Podlet({
name: 'myPodlet',
version: '1.0.0',
pathname: '/',
manifest: '/component.json',
});

app.get(podlet.manifest(), (req, res, next) => {
res.status(200).json(podlet);
});

Podium expects the podlet's manifest route to return a JSON document describing the podlet. This can be achieved by simply serializing the podlet instance.

const app = express();
const podlet = new Podlet([ ... ]);

app.get(podlet.manifest(), (req, res, next) => {
res.status(200).json(podlet);
});

The route will then respond with something like:

{
"name": "myPodlet",
"version": "1.0.0",
"content": "/",
"fallback": "/fallback",
"css": [],
"js": [],
"proxy": {}
}

options

optiontypedefaultrequired
prefixbooleanfalse
prefix

Sets whether the method should prefix the return value with the value for pathname that was set in the constructor.

Return the full pathname to the manifest (/foo/component.json):

const podlet = new Podlet({
name: 'myPodlet',
version: '1.0.0',
pathname: '/foo',
manifest: '/component.json',
});

podlet.manifest({ prefix: true });

.content(options)

This method returns the value of the content argument set in the constructor.

Set the content using the default pathname (/):

const app = express();
const podlet = new Podlet({
name: 'myPodlet',
version: '1.0.0',
pathname: '/',
});

app.get(podlet.content(), (req, res, next) => {
[ ... ]
});

Set the content path to /index.html:

const app = express();
const podlet = new Podlet({
name: 'myPodlet',
version: '1.0.0',
pathname: '/',
content: '/index.html',
});

app.get(podlet.content(), (req, res, next) => {
[ ... ]
});

Set the content path to /content and define multiple sub-routes each taking different URI parameters:

const app = express();
const podlet = new Podlet({
name: 'myPodlet',
version: '1.0.0',
pathname: '/',
content: '/content',
});

app.get('/content', (req, res) => { ... });
app.get('/content/info', (req, res) => { ... });
app.get('/content/info/:id', (req, res) => { ... });

options

optiontypedefaultrequired
prefixbooleanfalse
prefix

Specifies whether the method should prefix the return value with the pathname value that was set in the constructor.

Return the full pathname to the content (/foo/index.html):

const podlet = new Podlet({
name: 'myPodlet',
version: '1.0.0',
pathname: '/foo',
content: '/index.html',
});

podlet.content({ prefix: true });

The prefix will be ignored if the returned value is an absolute URL.

.fallback(options)

This method returns the value of the fallback argument set in the constructor.

Set the fallback to /fallback.html:

const app = express();
const podlet = new Podlet({
name: 'myPodlet',
version: '1.0.0',
pathname: '/',
fallback: '/fallback.html',
});

app.get(podlet.fallback(), (req, res, next) => {
[ ... ]
});

options

optiontypedefaultrequired
prefixbooleanfalse
prefix

Specifies whether the fallback method should prefix the return value with the value for pathname set in the constructor.

Return the full pathname to the fallback (/foo/fallback.html):

const podlet = new Podlet({
name: 'myPodlet',
version: '1.0.0',
pathname: '/foo',
fallback: '/fallback.html',
});

podlet.fallback({ prefix: true });

The prefix will be ignored if the returned value is an absolute URL.

.js(options|[options])

Set relative or absolute URLs to JavaScript assets for the podlet.

When set the values will be internally kept and made available for the document template to include. The assets set are also made available in the manifest for the layout to consume.

This method can be called multiple times with a single options object to set multiple assets or one can provide an array of options objects to set multiple assets.

options

optiontypedefaultrequireddetails
valuestringRelative or absolute URL to the JavaScript asset
prefixbooleanfalseWhether the pathname defined on the constructor should be prepend, if relative, to the value
typestringdefaultWhat type of JavaScript (eg. esm, default, cjs)
referrerpolicystringCorrelates to the same attribute on a HTML <script> element
crossoriginstringCorrelates to the same attribute on a HTML <script> element
integritystringCorrelates to the same attribute on a HTML <script> element
nomodulebooleanfalseCorrelates to the same attribute on a HTML <script> element
asyncbooleanfalseCorrelates to the same attribute on a HTML <script> element
deferbooleanfalseCorrelates to the same attribute on a HTML <script> element
value

Sets the pathname for the podlet's JavaScript assets. This value can be a URL at which the podlet's user facing JavaScript is served. The value can be either the pathname of a URL or an absolute URL.

Serve a javascript file at /assets/main.js:

const app = express();
const podlet = new Podlet({
name: 'myPodlet',
version: '1.0.0',
pathname: '/',
});

app.get('/assets.js', (req, res) => {
res.status(200).sendFile('./src/js/main.js', err => {});
});

podlet.js({ value: '/assets.js' });

Serve assets statically along side the app and set a relative URI to the JavaScript file:

const app = express();
const podlet = new Podlet({
name: 'myPodlet',
version: '1.0.0',
pathname: '/',
});

app.use('/assets', express.static('./src/js'));

podlet.js([
{ value: '/assets/main.js' },
{ value: '/assets/extra.js' },
]);

Set an absolute URL to where the javascript file is located:

const podlet = new Podlet({
name: 'myPodlet',
version: '1.0.0',
pathname: '/',
});

podlet.js({ value: 'http://cdn.mysite.com/assets/js/e7rfg76.js' });
prefix

Sets whether the method should prepend the value with the pathname value that was set in the constructor.

The prefix will be ignored if value is an absolute URL.

type

Set the type of script which is set. If not set, default will be used.

Use one of the following values:

  • esm for ECMAScript modules
  • cjs for CommonJS modules
  • amd for AMD modules
  • umd for Universal Module Definition
  • default if the type is unknown.

The type is a hint for further use of the script. This is normally used by the document template to print correct <script> tag or to give a hint to a bundler when optimizing JavaScript assets.

.css(options|[options])

Set relative or absolute URLs to Cascading Style Sheets (CSS) assets for the podlet.

When set the values will be internally kept and made available for the document template to include. The assets set are also made available in the manifest for the layout to consume.

The method can be called multiple times with a single options object to set multiple assets or one can provide an array of options objects to set multiple assets.

options

optiontypedefaultrequireddetails
valuestringRelative or absolute URL to the CSS asset
prefixbooleanfalseWhether the pathname defined on the constructor should be prepend, if relative, to the value
crossoriginstringCorrelates to the same attribute on a HTML <link> element
disabledbooleanfalseCorrelates to the same attribute on a HTML <link> element
hreflangstringCorrelates to the same attribute on a HTML <link> element
titlestringCorrelates to the same attribute on a HTML <link> element
mediastringCorrelates to the same attribute on a HTML <link> element
typestringtext/cssCorrelates to the same attribute on a HTML <link> element
relstringstylesheetCorrelates to the same attribute on a HTML <link> element
asstringCorrelates to the same attribute on a HTML <link> element
value

Sets the pathname for the CSS assets for the Podlet. The value can be a URL at which the podlet's user facing CSS is served. The value can be the pathname of a URL or an absolute URL.

Serve a CSS file at /assets/main.css:

const app = express();
const podlet = new Podlet({
name: 'myPodlet',
version: '1.0.0',
pathname: '/',
});

app.get('/assets.css', (req, res) => {
res.status(200).sendFile('./src/css/main.css', err => {});
});

podlet.css({ value: '/assets.css' });

Serve assets statically alongside the app and set a relative URI to the css file:

const app = express();
const podlet = new Podlet({
name: 'myPodlet',
version: '1.0.0',
pathname: '/',
});

app.use('/assets', express.static('./src/css'));

podlet.css([
{ value: '/assets/main.css' },
{ value: '/assets/extra.css' },
]);

Set an absolute URL to where the CSS file is located:

const podlet = new Podlet({
name: 'myPodlet',
version: '1.0.0',
pathname: '/',
});

podlet.css({ value: 'http://cdn.mysite.com/assets/css/3ru39ur.css' });
prefix

Sets whether the method should prepend the value with the pathname value that was set in the constructor.

The prefix will be ignored if value is an absolute URL.

.proxy({ target, name })

Method for defining proxy targets to be mounted in a layout server. For a detailed overview of how proxying works, please see the proxying guide for further details.

When a podlet is put in development mode (development is set to true in the constructor) these proxy endpoints will also be mounted in the podlet for ease of development and you will then have the same proxy endpoints available in development as you do when working with a layout.

Proxying is intended to be used as a way to make podlet endpoints publicly available. A common use case for this is creating endpoints for client side code to interact with (ajax requests from the browser). One might also make use of proxying to pass form submissions from the browser back to the podlet.

This method returns the value of the target argument and internally keeps track of the value of target for use when the podlet instance is serialized into a manifest JSON string.

In a podlet it is possible to define up to 4 proxy targets and each target can be the pathname part of a URL or an absolute URL.

For each podlet, each proxy target must have a unique name.

Mounts one proxy target /api with the name api:

const app = express();
const podlet = new Podlet( ... );
app.get(podlet.proxy({ target: '/api', name: 'api' }), (req, res) => { ... });

Defines multiple endpoints on one proxy target /api with the name api:

const app = express();
const podlet = new Podlet( ... );

app.get('/api', (req, res) => { ... });
app.get('/api/foo', (req, res) => { ... });
app.post('/api/foo', (req, res) => { ... });
app.get('/api/bar/:id', (req, res) => { ... });

podlet.proxy({ target: '/api', name: 'api' });

Sets a remote target by defining an absolute URL:

podlet.proxy({ target: 'http://remote.site.com/api/', name: 'remoteApi' });

.defaults(context)

Alters the default context set when in development mode.

By default this context has the following shape:

{
debug: 'false',
locale: 'en-EN',
deviceType: 'desktop',
requestedBy: 'the_name_of_the_podlet',
mountOrigin: 'http://localhost:port',
mountPathname: '/same/as/manifest/method',
publicPathname: '/same/as/manifest/method',
}

The default development mode context can be overridden by passing an object with the desired key / values to override.

Example of overriding deviceType:

const podlet = new Podlet({
name: 'foo',
version: '1.0.0',
});

podlet.defaults({
deviceType: 'mobile',
});

Additional values not defined by Podium can also be appended to the default development mode context in the same way.

Example of adding a context value:

const podlet = new Podlet({
name: 'foo',
version: '1.0.0',
});

podlet.defaults({
token: '9fc498984f3ewi',
});

N.B. The default development mode context will only be appended to the response when the constructor option development is set to true.

.pathname()

A helper method used to retrieve the pathname value that was set in the constructor.

Example:

const podlet = new Podlet({
name: 'myPodlet',
pathname: '/foo',
});

app.get(podlet.pathname(), (req, res, next) => {
[ ... ]
});

app.get(`${podlet.pathname()}/bar`, (req, res, next) => {
[ ... ]
});

app.get(`${podlet.pathname()}/bar/:id`, (req, res, next) => {
[ ... ]
});

.view(template)

Sets the default encapsulating HTML document template.

Its worth noting that this document template is only applied to Podlets when in development mode. When a Layout requests a Podlet this document template will not be applied.

Takes a template function that accepts an instance of HttpIncoming, a content string as well as any additional markup for the document's head section:

(incoming, body, head) => `Return an HTML string here`;

In practice this might look something like:

layout.view((incoming, body, head) => `<!doctype html>
<html lang="${incoming.context.locale}">
<head>
<meta charset="${incoming.view.encoding}">
<title>${incoming.view.title}</title>
${head}
</head>
<body>
${body}
</body>
</html>`;
);

.render(HttpIncoming, fragment, [args])

Method to render the document template. Will, by default, render the document template provided by Podium unless a custom document template is set using the .view method.

In most HTTP frameworks this method can be ignored in favour of res.podiumSend(). If present, res.podiumSend() has the advantage that it's not necessary to pass in an HttpIncoming object as the first argument.

Returns a String.

This method takes the following arguments:

HttpIncoming (required)

An instance of the HttpIncoming class.

app.get(podlet.content(), (req, res) => {
const incoming = res.locals.podium;
const document = layout.render(incoming, '<div>content to render</div>');
res.send(document);
});

fragment

An String that is intended to be a fragment of the final HTML document.

layout.render(incoming, '<div>content to render</div>');

[args]

All following arguments given to the method will be passed on to the document template. For example, this could be used to pass on parts of a page to the document template.

podlet.view = (incoming, body, head) => {
return `
<html>
<head>${head}</head>
<body>${body}</body>
</html>
`;
};

app.get(podlet.content(), async (req, res, next) => {
const incoming = res.locals.podium;

const head = `<meta ..... />`;
const body = `<section>my content</section>`;

const document = layout.render(incoming, body, head);
res.send(document);
});

.process(HttpIncoming)

Method for processing an incoming HTTP request. This method is intended to be used to implement support for multiple HTTP frameworks and in most cases will not need to be used directly by podlet developers when creating podlet servers.

What it does:

  • Handles detection of development mode and sets the appropriate defaults
  • Runs context deserializing on the incoming request and sets a context object at HttpIncoming.context.

Returns an HttpIncoming object.

This method takes the following arguments:

HttpIncoming (required)

An instance of the HttpIncoming class.

import { HttpIncoming } from '@podium/utils';
import Podlet from '@podium/podlet';

const podlet = new Podlet({
name: 'myPodlet',
version: '1.0.0',
pathname: podlet.content(),
});

app.use(async (req, res, next) => {
const incoming = new HttpIncoming(req, res, res.locals);
try {
await podlet.process(incoming);
if (!incoming.proxy) {
res.locals.podium = result;
next();
}
} catch (error) {
next(error);
}
});

res.podiumSend(fragment)

Method for dispatching an HTML fragment. Calls the .send() / .write() methods in the framework that's being used and serves the HTML fragment.

When in development mode, when the constructor option development is set to true, this method will wrap the provided fragment in the given document template before dispatching. When not in development mode, this method will just dispatch the fragment.

Example of sending an HTML fragment:

app.get(podlet.content(), (req, res) => {
res.podiumSend('<h1>Hello World</h1>');
});

Development mode

In most cases podlets are fragments of a whole HTML document. When a layout server is requesting a podlet's content or fallback, the podlet should serve just that fragment and not a whole HTML document with its <html>, <head> and <body>. Additionally, when a layout server requests a podlet it provides a Podium context to the podlet.

These things can prove challenging for local development since accessing a podlet directly, from a web browser, in local development will render the podlet without either an encapsulating HTML document or a Podium context that the podlet might need to function properly.

To solve this it is possible to switch a podlet to development mode by setting the development argument in the constructor to true.

When in development mode a default context on the HTTP response will be set and an encapsulating HTML document will be provided (so long as res.podiumSend() is used) when dispatching the content or fallback.

The default HTML document for encapsulating a fragment will reference the values set on .css() and .js() and use locale from the default context to set language on the document.

The default context in development mode can be altered by the .defaults() method of the podlet instance.

The default encapsulating HTML document used in development mode can be replaced by the .view() method of the podlet instance.

Note: Only turn on development mode during local development, ensure it is turned off when in production.

Example of turning on development mode only in local development:

const podlet = new Podlet({
development: process.env.NODE_ENV !== 'production';
});

When a layout server sends a request to a podlet in development mode, the default context will be overridden by the context from the layout server and the encapsulating HTML document will not be applied.