Skip to main content

​
Overview

Univerto is designed from the ground up for optimal tree-shaking. The library uses a modular export structure that allows modern bundlers to eliminate unused code, ensuring you only ship what you use.

​
Modular Export Structure

Univerto provides separate export paths for each unit converter instead of a single monolithic import. This architecture enables bundlers to perform effective dead code elimination.

​
Available Export Paths

Each converter has its own subpath export: 
// Time units
import { TimeUnitConverter, TIME_UNIT } from 'univerto/time'

// Length units
import { LengthUnitConverter, LENGTH_UNIT } from 'univerto/length'

// Area units
import { AreaUnitConverter, AREA_UNIT } from 'univerto/area'

// Volume units
import { VolumeUnitConverter, VOLUME_UNIT } from 'univerto/volume'

// Mass units
import { MassUnitConverter, MASS_UNIT } from 'univerto/mass'

// Speed units
import { SpeedUnitConverter, SPEED_UNIT } from 'univerto/speed'

// Data units
import { DataUnitConverter, DATA_UNIT } from 'univerto/data'

// Voltage units
import { VoltageUnitConverter, VOLTAGE_UNIT } from 'univerto/voltage'

// Current units
import { CurrentUnitConverter, CURRENT_UNIT } from 'univerto/current'

// Frequency units
import { FrequencyUnitConverter, FREQUENCY_UNIT } from 'univerto/frequency'

​
Bundle Size Impact

​
❌ Avoid Barrel Imports

Don’t import from the main entry point if you only need specific converters: 
// This imports ALL converters (not recommended)
import { TimeUnitConverter, LengthUnitConverter } from 'univerto'

​
✅ Use Specific Imports

Import only what you need from subpaths: 
// This imports ONLY the time converter (recommended)
import { TimeUnitConverter, TIME_UNIT } from 'univerto/time'

​
Bundle Size Comparison

Import StrategyApproximate Bundle Size
Single converter (e.g., univerto/time)~2-3 KB (minified + gzipped)
Three converters (e.g., time, length, mass)~6-8 KB (minified + gzipped)
All converters via barrel import~15-20 KB (minified + gzipped)
Exact bundle sizes depend on your bundler configuration and which converters you import. The library itself has zero dependencies, so there are no transitive dependency costs.

​
How It Works

Univerto’s package.json defines explicit export maps for each converter: 
{
  "exports": {
    "./time": {
      "import": "./dist/units/time.js",
      "require": "./dist/units/time.cjs"
    },
    "./length": {
      "import": "./dist/units/length.js",
      "require": "./dist/units/length.cjs"
    }
    // ... other converters
  }
}
Modern bundlers (Webpack 5+, Vite, Rollup, esbuild) respect these export maps and can:
  1. Resolve the exact file for each subpath
  2. Analyze which files are actually imported
  3. Eliminate code from unused files during the build

​
Best Practices

Import by subpath

Always use specific subpath imports like univerto/time rather than the main univerto entry

Import only what you need

If your app only converts time units, only import the time converter

Use named imports

Use import { TimeUnitConverter } rather than import * to help bundlers identify used exports

Check bundle analyzer

Use tools like webpack-bundle-analyzer to verify Univerto’s size in your production bundle

​
Bundler Configuration

​
Vite

Vite supports tree-shaking out of the box with ES modules. No configuration needed: 
// vite.config.ts
import { defineConfig } from 'vite'

export default defineConfig({
  build: {
    minify: 'terser', // or 'esbuild'
    // Tree-shaking is automatic with ES modules
  }
})

​
Webpack 5

Webpack 5 has improved tree-shaking with the sideEffects flag. Univerto sets "sideEffects": false in its package.json, indicating all modules are safe to tree-shake: 
// webpack.config.js
module.exports = {
  mode: 'production',
  optimization: {
    usedExports: true, // Enable tree-shaking
    minimize: true
  }
}

​
Rollup

Rollup excels at tree-shaking ES modules: 
// rollup.config.js
import { terser } from 'rollup-plugin-terser'

export default {
  plugins: [
    terser() // Minification removes dead code
  ],
  // Tree-shaking is automatic
}

​
esbuild

esbuild performs tree-shaking automatically: 
// build.js
require('esbuild').build({
  entryPoints: ['src/index.ts'],
  bundle: true,
  minify: true,
  treeShaking: true // Default is true
})

​
Verifying Tree-Shaking

​
Using Webpack Bundle Analyzer

npm install --save-dev webpack-bundle-analyzer

// webpack.config.js
const BundleAnalyzerPlugin = require('webpack-bundle-analyzer').BundleAnalyzerPlugin

module.exports = {
  plugins: [
    new BundleAnalyzerPlugin()
  ]
}
After building, check the visualization to ensure only the converters you imported are included.

​
Using Rollup Plugin Visualizer

npm install --save-dev rollup-plugin-visualizer

// rollup.config.js
import { visualizer } from 'rollup-plugin-visualizer'

export default {
  plugins: [
    visualizer({ open: true })
  ]
}

​
Zero Dependencies Advantage

Univerto has zero runtime dependencies. This means:
  • No dependency tree to manage
  • No transitive dependency security vulnerabilities
  • No version conflicts with your other packages
  • Smaller total bundle size
  • Faster npm install times
The zero-dependency approach combined with modular exports makes Univerto one of the most bundle-size-friendly unit conversion libraries available.

Installation

Learn how to install Univerto

TypeScript Support

Explore TypeScript integration and type safety

Build docs developers (and LLMs) love

Get started for freeTalk to us