Contents of the docs
esbuild-plugin-time · Docs
Usage
Typical uses of esbuild-plugin-time – one bundle, several bundles, watch mode and the right position in plugins.
One bundle
Without a name the plugin only prints "Build started" and the duration:
import esbuild from 'esbuild';
import time from 'esbuild-plugin-time';
await esbuild.build({
entryPoints: ['./src/index.js'],
bundle: true,
outfile: './dist/index.js',
plugins: [
time(),
],
});Build started
Build ended: 42msSeveral bundles
If several builds run at the same time, give each a name:
await Promise.all([
esbuild.build({
entryPoints: ['./src/index.js'],
bundle: true,
outfile: './dist/index.js',
plugins: [time('App')],
}),
esbuild.build({
entryPoints: ['./src/worker.js'],
bundle: true,
outfile: './dist/worker.js',
plugins: [time('Worker')],
}),
]);The output then looks something like this:
Build started for App
Build started for Worker
Build ended Worker: 12ms
Build ended App: 40msPosition in plugins
esbuild calls the plugins' onEnd callbacks one after another, in the order they appear in plugins. If time() comes
first, the measurement ends before the other plugins have finished their onEnd. To include, for example, the copying
done by esbuild-plugin-copy, put time() last:
plugins: [
clear('./dist'),
copy({from: './public', to: '.'}),
time('App'),
],Watch mode
With esbuild.context() and watch() the two lines appear on every rebuild, so you see right away that a change has
arrived.
const ctx = await esbuild.context({
entryPoints: ['./src/index.js'],
bundle: true,
outfile: './dist/index.js',
plugins: [
time('App'),
],
});
await ctx.watch();