@asset-pipe/client
Asset pipe client
Last updated 4 months ago by digitalsadhu .
MIT · Repository · Bugs · Original npm · Tarball · package.json
$ cnpm install @asset-pipe/client 
SYNC missed versions from official npm registry.

@asset-pipe/client

Travis CI Build Status NPM version Dependency Status Dev Dependency Status

Greenkeeper badge

A client for reading an asset file entry point and uploading it as an asset feed to a asset-pipe-build-server and for triggering builds of executable asset bundles in the said server.

Creating asset bundles with asset-pipe is a two step process. The first step is to upload an asset feed to the asset-pipe-build-server. On upload the asset-feed will be persisted and the asset-pipe-build-server will return the generated filename of the uploaded asset-feed.

The second step is then to create a bundle out of one or multiple asset-feeds. This is done by providing the unique ID(s) of the asset-feeds one wants to use to build an asset bundle to the asset-pipe-build-server. The build server will then create an executable asset bundle out of these asset-feeds and persist this. It will respond with the URL to the bundle.

This client helps with remotely triggering these steps in the asset-pipe-build-server.

Optimistic Bundling

The asset server can produce asset bundles in what we call an "optimistic" fashion. This means that asset bundles will be automatically produced and reproduced any time an asset changes or any time the definition of which assets should be included in a bundle changes.

This works in the following way:

  1. Any number of assets are uploaded to the asset server using the client.publishAssets method.
  2. Bundling instructions are uploaded to the asset server using the client.publishInstructions method.

Steps 1 and 2 can be performed in any order and the asset server will automatically bundle and rebundle as needed to produce up to date bundles for any instructions that have been published to the server.

Examples

We might begin by first we publishing some bundling instructions. (Though we could just as easily publish assets first):

await client.publishInstructions('layout', 'js', ['podlet1', 'podlet2']);

At this point, the server will not have created any bundles as there are no corresponding assets for podlet1 or podlet2.

Next we upload the missing asset feeds for podlet1 and podlet2.

const { uri, id } = await client.publishAssets('podlet1', ['/path/to/file.js']);
const { uri, id } = await client.publishAssets('podlet2', ['/path/to/file.js']);

Once both these asset feeds are in place, the asset server will generate a fresh bundle based on our earlier published instructions. Once finished, a new bundle file will be available from the asset server.

Calculating the location of produced bundle files

When publishAssets is successfully called, a unique asset hash id property will be available on the returned object. sha256 hashing all asset hashes together (in the same order they are defined in the publish instructions) and appending the correct file extension to the result will give you the filename of the resulting bundle.

Example

First publish assets and instructions

await client.publishInstructions('layout', 'js', ['podlet1', 'podlet2']);
const result1 = await client.publishAssets('podlet1', ['/path/to/file.js']);
const result2 = await client.publishAssets('podlet2', ['/path/to/file.js']);

Next, compute a hash and resulting filename

const hash = sha256Somehow(result1.id, result2.id);
const bundleFilename = `${hash}.js`;

Finally, the file can be retrieved from the asset server via the /bundle endpoint.

GET http://<asset-server-url>/bundle/<hash>.js

To make some of this a little easier, 2 helper methods exist on the client:

  • bundleURL - calculates the url location for a bundle based on a given array of asset hashes.
  • bundlingComplete - determines if bundling is complete for a given array of asset hashes.

See API documentation below for more information.

Installation

$ npm install @asset-pipe/client

Example I

Read an CommonJS module entry point and upload it as an asset-feed to the asset-pipe-build-server:

const Client = require('@asset-pipe/client');

const client = new Client({
    serverId: 'my-app-1',
    server: 'http://127.0.0.1:7100'
});

client
    .uploadFeed(['path/to/myFrontendCode.js'])
    .then(content => {
        // content contains filename of created the asset-feed
        console.log(content);
    })
    .catch(error => {
        console.log(error);
    });

Example II

Read a CSS file entry point and upload it as an asset-feed to the asset-pipe-build-server:

const Client = require('@asset-pipe/client');

const client = new Client({
    server: 'http://127.0.0.1:7100'
});

client
    .uploadFeed(['/path/to/styles.css'])
    .then(content => {
        // content contains filename of created the asset-feed
        console.log(content);
    })
    .catch(error => {
        console.log(error);
    });

Example III

Build a javascript bundle out of two asset feeds:

const Client = require('@asset-pipe/client');
const client = new Client({
    serverId: 'my-app-2',
    server: 'http://127.0.0.1:7100'
});

bundle
    .createRemoteBundle(
        [
            'f09a737b36b7ca19a224e0d78cc50222d636fd7af6f7913b01521590d0d7fe02.json',
            'c50ca03a63650502e1b72baf4e493d2eaa0e4aa38aa2951825e101b1d6ddb68b.json'
        ],
        'js'
    )
    .then(content => {
        // content contains URI to the created bundle
        console.log(content);
    })
    .catch(error => {
        console.log(error);
    });

Example IIII

Build a CSS bundle out of two asset feeds:

const Client = require('@asset-pipe/client');
const client = new Client({
    server: 'http://127.0.0.1:7100'
});

bundle
    .createRemoteBundle(
        [
            'f09a737b36b7ca19a224e0d78cc50222d636fd7af6f7913b01521590d0d7fe02.json',
            'c50ca03a63650502e1b72baf4e493d2eaa0e4aa38aa2951825e101b1d6ddb68b.json'
        ],
        'css'
    )
    .then(content => {
        // content contains URI to the created bundle
        console.log(content);
    })
    .catch(error => {
        console.log(error);
    });

API

Under the hood, when working with javascript, the asset-pipe project builds on browserify. Multiple methods in this module are therefor underlaying Browserify methods where all features found in Browserify can be used. Such methods will in this documentation point to the related documentation in Browserify.

When working with CSS the underlying POST CSS is used but the implementation is not exposed so there are no additional supported methods.

This module has the following API:

constructor(options)

Supported arguments are:

  • options.server - Required URI to the asset-pipe-build-server
  • options.serverId - An optional unique name to identify the deployed server (required for runtime optimistic bundling)
  • options.minify - Use minification (optimistic bundling only) true|false Not providing this option will result in server default being used.
  • options.sourceMaps - (experimental) Use sourceMaps (optimistic bundling only) true|false Not providing this option will result in server default being used.
  • options.logger - An optional log4js compatible logger. See abslog for more information
  • options.development - Puts the client in development mode. For use with the client.middleware() function (see below). Default false
  • options.tag - Optionally define a tag to be used when publishing assets to an asset server. For use with the client.middleware() function (see below). Required when publish is true.
  • options.js - Optionally define the full path to a JavaScript file. For use with the client.middleware() function (see below)
  • options.css - Optionally define the full path to a CSS style file. For use with the client.middleware() function (see below)

transform()

Same as the Browserify transform method. NOTE: Only applicable when uploading javascript feeds.

plugin()

Same as the Browserify plugin method. NOTE: Only applicable when uploading javascript feeds.

uploadFeed(files)

Read the CommonJS module or CSS file entry point and uploads it as an asset feed to the asset-pipe-build-server.

  • files - Array - Either list of CommonJS module entry points - Same as files in the Browserify constructor OR list of paths to CSS files

Returns a promise.

createRemoteBundle(feeds, type)

Creates an asset bundle on the asset-pipe-build-server.

  • feeds - Array - List of asset-feed filenames.
  • type - string - Either 'js' or 'css'

sync()

Fetches centralised configuration information from the asset server. This should be called after creating a new client instance and before any calls to .bundleURL() or .bundlingComplete()

Example

const client = new Client(options);
await client.sync();

publishAssets(tag, entrypoints, options)

Publishes assets to the asset server for use in optimisitic bundling. Bundles will be created according to bundle instructions published using the publishInstructions method.

  • tag - string - Alphanumeric string identifying the publisher. Should be unique.
  • entrypoints - Array|string - Array of asset entrypoint filenames or single asset entrypoint filename string to be published to the asset server.
  • options - object - Bundling options. {minify: true|false, sourceMaps: true|false} Setting these options here will override the same options provided to the constructor

return - object - An object with keys id (refering to the unique asset hash) and uri (referring to the location of the published asset on the server).

Examples

JavaScript

const { uri, id } = await client.publishAssets('podlet1', '/path/to/file.js');

CSS

const { uri, id } = await client.publishAssets('podlet1', '/path/to/file.css');

With minification

const { uri, id } = await client.publishAssets('podlet1', '/path/to/file.js', {
    minify: true
});

publishInstructions(tag, type, data, options)

Publishes bundling instructions to the asset server for use in optimisitic bundling. Bundles are generated as specified by the data array. Anytime new instructions are published (via publishInstructions) or assets are published (via publishAssets), new bundles will be generated by the server.

  • tag - string - Alphanumeric string identifying the publisher. Should be unique.
  • type - string - Asset type. Valid values are 'js' and 'css'
  • data - array - Array of tags to bundle together. Each tag must refer to the tag property given when publishing assets using the publishAssets method.
  • options - object - Bundling options. {minify: true|false, sourceMaps: true|false} Setting these options here will override the same options provided to the constructor

return - 204 No Content is returned when publishing has successfully completed.

Examples

JavaScript

await client.publishInstructions('layout', 'js', ['podlet1', 'podlet2']);

CSS

await client.publishInstructions('layout', 'css', ['podlet1', 'podlet2']);

With minification

await client.publishInstructions('layout', 'js', ['podlet1', 'podlet2'], {
    minify: true
});

bundleURL(feedHashes, options)

Calculates a bundle url string based on a given array of hashes which are asset feed content hashes. Each time an asset feed is published using client.publishAssets the resolved object will contain an id property which is the hash of the feed content and can be used with this method.

Calculation is done by sha256 hashing together the given hashes and dropping the resulting hash into a url template.

As such, this method does not perform any requests to the server and therefore cannot guarantee that the bundle exists on the server.

Note: You should call await client.sync(); one time after creating the client instance, before calling bundleURL to ensure the client has update information about the public location of bundle files.

  • hashes - string[] - array of asset feed content hashes as returned by client.publishAssets
  • options - object
    • options.prefix - string url prefix to use when building bundle url. Defaults to ${client.server}/bundle/ which is the location on the asset server that a bundle can be located. Overwrite this if you use a CDN and need to point to that.
    • options.type - string (js|css) - file type. Defaults to js

return - Promise<string> - url for asset bundle on asset server.

Example

// publish instructions
await client.publishInstructions('layout', 'js', ['podlet1', 'podlet2']);

// publish necessary assets
const { uri, id1 } = await client.publishAssets('podlet1', [
    '/path/to/file.js'
]);
const { uri, id2 } = await client.publishAssets('podlet2', [
    '/path/to/file.js'
]);

// calculate the url of the finished bundle
const url = await client.bundleURL([id1, id2]);

bundlingComplete(feedhashes, options)

Calculates whether a bundling for the given feedHashes has been completed. The rules for this method are as follows:

Note: You should call await client.sync(); one time after creating the client instance, before calling bundleURL to ensure the client has update information about the public location of bundle files.

  • If feedHashes is an empty array, this method resolves to true as no bundle needs to be built.

  • Otherwise, if feedHashes is not an empty array then a bundle url will be computed and a request made to check if the file exists on the server.

  • hashes - string[] - array of asset feed content hashes as returned by client.publishAssets

  • options - object

    • options.prefix - string url prefix to use when building bundle url. Defaults to ${client.server}/bundle/ which is the location on the asset server that a bundle can be located. Overwrite this if you use a CDN and need to point to that.
    • options.type - string (js|css) - file type. Defaults to js

return - Promise<boolean> - resolves to a boolean representing whether the bundling process for the given feedHashes is considered to be complete.

Example

// publish instructions
await client.publishInstructions('layout', 'js', ['podlet1', 'podlet2']);

// publish necessary assets
const { uri, id1 } = await client.publishAssets('podlet1', [
    '/path/to/file.js'
]);
const { uri, id2 } = await client.publishAssets('podlet2', [
    '/path/to/file.js'
]);

// calculate the url of the finished bundle
const isComplete = await client.bundlingComplete([id1, id2]);

.middleware()

This method returns a connect middleware that can be used to both support assets in local development and to ensure assets are published before the request completes.

When .middleware() is called and the client flag development is set to true then assets will be provided at /js and /css on your app. Additionally, file system watching will be enabled for JavaScript.

N.B. You must call .publish() and provide js and/or css options for development mode to work.

Example

const client = new Client({
    ...
    development: true,
    ...
});

client.publish({
    js: '/path/to/script.js',
    css: '/path/to/style.js',
});

app.use(client.middleware());

// curl http:<address>:<port>/js => bundled js scripts
// curl http:<address>:<port>/css => bundled css styles

When .middleware() is called and the client flag development is false then the middleware will force requests to wait until client.ready() resolves to true. This will ensure that any publishing or bundling has completed before route handlers are invoked.

Example

const client = new Client({
    ...
    server: 'http://asset-server.com:1234',
    tag: 'uniqueLabel',
    development: false,
    ...
});

client.publish({ ... });
client.bundle({ ... });

app.use(client.middleware());

app.get('/', (req, res) => {
    // publishing and bundling have completed before we get
    // here
})

.js()

Method for retrieving the id hash for JavaScript assets uploaded to an asset server

const client = new Client({
    ...
    server: 'http://asset-server.com:1234',
    tag: 'uniqueLabel',
    development: false,
    ...
})

client.publish({ ... });
client.js() // => null

app.use(client.middleware());

app.get('/', (req, res) => {
    client.js() // a2b2ab2a2b2b3bab4ab4aa22babab2ba2
})

.css()

Method for retrieving the id hash for CSS assets uploaded to an asset server

const client = new Client({
    ...
    server: 'http://asset-server.com:1234',
    tag: 'uniqueLabel',
    development: false,
    ...
})

client.publish({ ... });
client.css() // => null

app.use(client.middleware());

app.get('/', (req, res) => {
    client.css() // b2b2ac2a2b4b3bab4ab2aa22babab2ba2
})

.ready()

Method for waiting until assets have finished publishing to or bundling on an asset server.

const client = new Client({
    ...
    server: 'http://asset-server.com:1234',
    tag: 'uniqueLabel',
    development: false,
    ...
});

client.publish({ ... });

client.css() // => null

await client.ready();

client.js() // a2b2ab2a2b2b3bab4ab4aa22babab2ba2
client.css() // b2b2ac2a2b4b3bab4ab2aa22babab2ba2

.publish(options)

Method to publish JavaScript and/or CSS assets to an asset server. Returns a promise which resolves when publishing is done.

const client = new Client({
    server: 'http://asset-server.com:1234',
    tag: 'uniqueLabel'
});

const { js, css } = await client.publish({
    js: '/path/to/script.js',
    css: '/path/to/styles.css'
});
// js => a2b2ab2a2b2b3bab4ab4aa22babab2ba2
// css => b2b2ac2a2b4b3bab4ab2aa22babab2ba2

It is not necessary to wait for publish to complete. You can also call publish to kick off publishing and then wait for the .ready() method to resolve to know when publishing is complete.

const client = new Client({
    server: 'http://asset-server.com:1234',
    tag: 'uniqueLabel'
});

client.publish({
    js: '/path/to/script.js',
    css: '/path/to/styles.css'
});

await client.ready();

If you use .middleware() in your connect based applications, waiting for publish completion will happen automatically.

const client = new Client({
    server: 'http://asset-server.com:1234',
    tag: 'uniqueLabel'
});

client.publish({
    js: '/path/to/script.js',
    css: '/path/to/styles.css'
});

app.use(client.middleware());

.bundle(options)

Method to instruct an asset server to bundle JavaScript and/or CSS assets. Returns a promise which resolves when bundling is done.

const client = new Client({
    server: 'http://asset-server.com:1234',
    tag: 'uniqueLabel'
});

await client.bundle({ js: ['tag1', 'tag2'], css: ['tag1', 'tag2'] });

It is not necessary to wait for bundle to complete. You can also call bundle to kick off bundling and then wait for the .ready() method to resolve to know when bundling is complete.

const client = new Client({
    server: 'http://asset-server.com:1234',
    tag: 'uniqueLabel'
});

client.bundle({ js: ['tag1', 'tag2'], css: ['tag1', 'tag2'] });

await client.ready();

If you use .middleware() in your connect based applications, waiting for bundle completion will happen automatically.

const client = new Client({
    server: 'http://asset-server.com:1234',
    tag: 'uniqueLabel'
});

client.bundle({ js: ['tag1', 'tag2'], css: ['tag1', 'tag2'] });

app.use(client.middleware());

.scripts(hashes)

Method to retrieve JavaScript bundle URLs once publishing and bundling are complete. Includes a best effort algorithm to try to return an optimally bundled solution, falling back to multiple individual bundles when an optimal bundle is not available.

Example: Requesting a bundling for 2 tags when only 1 has been published

const client = new Client({
    server: 'http://asset-server.com:1234',
    tag: 'tag1'
});

const { js } = await client.publish({ ... });
await client.bundle({ js: ['tag1', 'tag2'] });

const scripts = client.scripts([js]);
// scripts => [http://<asset-server-url>/bundle/${js}.js]

This method will always return an array so you can iterate over it in your templates and create script tags

{% for script in scripts %}
    <script src={{ script }}></script>
{% endfor %}

.styles(hashes)

Method to retrieve css bundle URLs once publishing and bundling are complete. Includes a best effort algorithm to try to return an optimally bundled solution, falling back to multiple individual bundles when an optimal bundle is not available.

Example: Requesting a bundling for 2 tags when only 1 has been published

const client = new Client({
    server: 'http://asset-server.com:1234',
    tag: 'tag1'
});

const { css } = await client.publish({ ... });
await client.bundle({ css: ['tag1', 'tag2'] });

const styles = client.styles([css]);
// styles => [http://<asset-server-url>/bundle/${css}.css]

This method will always return an array so you can iterate over it in your templates and create style tags

{% for style in styles %}
    <link rel="stylesheet" href={{ style }} />
{% endfor %}

.metrics

This module uses @metrics/client to expose metric objects for consumption via a stream.

Available metric names are:

  • publish_assets_timer
  • publish_instructions_timer
  • asset_server_sync_timer

Example: piping metrics stream into a consumer

client.metrics.pipe(consumer);

See @metrics/client for more details including how to implement a consumer.

Transpilers

Since asset-pipe is built on browserify under the hood, its fully possible to take advantage of the different transpiers available for browserify when working with javascript.

As an example, here is how Babel is applied:

const babelify = require('babelify');
const Client = require('@asset-pipe/client');

const client = new Client({ server: 'http://127.0.0.1:7100' });

client.transform(babelify, { presets: ['es2015'] });

const { uri, id } = await client.publishAssets('podlet1', ['/path/to/file.js']);

Contributing

The contribution process is as follows:

  • Fork this repository.
  • Make your changes as desired.
  • Run the tests using npm test. This will also check to ensure that 100% code coverage is maintained. If not you may need to add additional tests.
  • Stage your changes.
  • Run git commit or, if you are not familiar with semantic commit messages, please run npm run cm and follow the prompts instead which will help you write a correct semantic commit message.
  • Push your changes and submit a PR.

Current Tags

  • 4.5.0                                ...           latest (4 months ago)

36 Versions

  • 4.5.0                                ...           4 months ago
  • 4.4.1                                ...           10 months ago
  • 4.4.0                                ...           a year ago
  • 4.3.1                                ...           a year ago
  • 4.3.0                                ...           a year ago
  • 4.2.3                                ...           a year ago
  • 4.2.2                                ...           a year ago
  • 4.2.1                                ...           2 years ago
  • 4.2.0                                ...           2 years ago
  • 4.1.0                                ...           2 years ago
  • 4.0.2                                ...           2 years ago
  • 4.0.1                                ...           2 years ago
  • 4.0.0                                ...           2 years ago
  • 3.7.0                                ...           2 years ago
  • 3.6.0                                ...           2 years ago
  • 3.5.2                                ...           2 years ago
  • 3.5.1                                ...           2 years ago
  • 3.5.0                                ...           2 years ago
  • 3.4.2                                ...           2 years ago
  • 3.4.1                                ...           2 years ago
  • 3.4.0                                ...           2 years ago
  • 3.3.0                                ...           2 years ago
  • 3.2.0                                ...           2 years ago
  • 3.1.1                                ...           2 years ago
  • 3.1.0                                ...           2 years ago
  • 3.0.8                                ...           2 years ago
  • 3.0.7                                ...           2 years ago
  • 3.0.6                                ...           2 years ago
  • 3.0.5                                ...           2 years ago
  • 3.0.4                                ...           2 years ago
  • 3.0.3                                ...           3 years ago
  • 3.0.2                                ...           3 years ago
  • 3.0.1                                ...           3 years ago
  • 3.0.0                                ...           3 years ago
  • 2.1.0                                ...           3 years ago
  • 1.0.0                                ...           3 years ago
Maintainers (2)
Downloads
Today 0
This Week 1
This Month 1
Last Day 1
Last Week 36
Last Month 74
Dependencies (13)
Dev Dependencies (20)
Dependents (0)
None

Copyright 2014 - 2016 © taobao.org |