$ pnpm run build:cross-env --mode ${NODE_ENV:-development}
$ vite build --config vite.esm.config.ts --mode production
ViteEsmConfig: .
{
  tsConfigPaths: [
    '/home/runner/work/captcha/captcha/packages/locale/tsconfig.json',
    '/home/runner/work/captcha/captcha/packages/util/tsconfig.json',
    '/home/runner/work/captcha/captcha/packages/logger/tsconfig.json',
    '/home/runner/work/captcha/captcha/packages/types/tsconfig.json',
    '/home/runner/work/captcha/captcha/packages/util-crypto/tsconfig.json'
  ]
}
{
  externals: [
    '@prosopo/locale',
    '@prosopo/util',
    '@prosopo/logger',
    '@prosopo/types',
    '@prosopo/util-crypto'
  ]
}
The plugin "vite-tsconfig-paths" is detected. Vite now supports tsconfig paths resolution natively via the resolve.tsconfigPaths option. You can remove the plugin and set resolve.tsconfigPaths: true in your Vite config instead.
vite v8.1.5 building ssr environment for production...
Bundle build started

transforming...Build end
✓ 8 modules transformed.
rendering chunks...
computing gzip size...
dist/utils/utils.js                 0.01 kB │ gzip: 0.03 kB
dist/_virtual/_rolldown/runtime.js  0.04 kB │ gzip: 0.06 kB
dist/utils/time.js                  0.14 kB │ gzip: 0.11 kB
dist/utils/.export.js               0.47 kB │ gzip: 0.19 kB
dist/utils/batches.js               0.61 kB │ gzip: 0.32 kB
dist/index.js                       0.68 kB │ gzip: 0.24 kB
dist/utils/objectUtils.js           1.49 kB │ gzip: 0.57 kB
dist/error.js                       6.71 kB │ gzip: 2.01 kB

✓ built in 73ms