Numeral.js module bundle (see jenkins-js-modules).

Note: DEPRECATED This JavaScript library can now be easily externalized via the package.json.

import this bundle (see jenkins-js-modules) into your application bundle (in your plugin etc) instead of bundling Numeral.js in your application bundle, making your app bundle considerably lighter.

HPI Dependency

Your plugin needs to add a dependency on this plugin (to ensure it gets installed in Jenkins).

<artifactItem>
    <groupId>org.jenkins-ci.ui</groupId>
    <artifactId>numeraljs</artifactId>
    <version>[VERSION]</version>
</artifactItem>

See wiki.jenkins-ci.org to get the latest version.

Using Numeral.js v1:

• Bundle Id: numeraljs:numeraljs1

There are 2 ways of using numeraljs:numeraljs1 in your app bundle:

1. Normal require syntax (synchronous) on the standard numeral NPM module, and then using a withExternalModuleMapping instruction (jenkins-js-builder) in the app bundle's gulpfile.js.
2. Lower level import syntax (asynchronous).

require (sync)

If using jenkins-js-builder to create yor application bundle, you can code your application's CommonJS modules to use the more simple CommonJS style require syntax (synch), as opposed to the lower level import syntax (async) of jenkins-js-modules.

When doing it this way, your module code should require the numeral NPM module and use it as normal e.g.

var numeral = require('numeral');
var number = 12345.86578;
var formatted = numeral(number).format('0.00');

Note: You should install numeral as a dev dependency i.e. npm install --save-dev numeral

The above code will work fine as is, but the only downside is that your app bundle will be very bloated as it will include the numeral NPM module. To lighten your bundle for the browser (by using a shared instance of the numeral NPM module), use jenkins-js-builder to create your app bundle (in your gulpfile.js), telling it to "map" (transform) all synchronous require calls for numeral to async imports of the numeraljs:numeraljs1 bundle (which actually exports numeral) e.g.

var builder = require('jenkins-js-builder');

//
// Use the predefined tasks from jenkins-js-builder.
//
builder.defineTasks(['test', 'bundle']);

//
// Create the app bundle, mapping sync require calls for 'numeral' to
// async imports of 'numeraljs:numeraljs1'.
//
builder.bundle('src/main/js/myapp.js')
    .withExternalModuleMapping('numeral', 'numeraljs:numeraljs1')
    .inDir('src/main/webapp/bundles');

All of the above "magically" translates the appropriate bits of your app bundle's JS code to use async import calls (see below) in a way that just works.

import (async)

You can also use the lower level asynchronous import call (jenkins-js-modules) to get your numeral reference.

require('jenkins-js-modules')
    .import('numeraljs:numeraljs1')
    .onFulfilled(function(numeral) {
        var formatted = numeral(number).format('0.00');
    });

Note: Using this async import approach makes unit testing of your JavaScript modules more tricky because your test scaffolding code will need to manually export the numeral module as numeraljs:numeraljs1 in order for the subsequent import to work without failure. This is not an issue when using the synchronous require approach (see above) because the bundle import is only introduced to the JS code as the bundle is being created.