Registry / devops / kaba-babel-preset

kaba-babel-preset

library4.1.4jsnpmunverified

A custom Babel preset for use with the Kaba build system, currently at v4.1.4. Provides legacy and modern environment configurations via `@babel/preset-env` and includes support for React, nullish coalescing, and numeric separators. Peer dependency on `core-js ^3.16.1`. Key differentiator: returns separate configs for legacy and modern browsers, allowing differential serving. Release cadence is irregular, with minor and patch updates as needed.

devops

npm install kaba-babel-preset

github ↗package ↗

INSTALL

IMPORT

SIG · KABA-BABEL-PRESET

kaba-babel-preset

devopsjavascriptv4.1.4

Install

—

Import

—

Disk

—

Pass rate

0/ 6

Env Coverage0 / 6

glibc

18–22

musl

18–22

Install & Compatibility

Where this runs

tested against v? · npm install

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

node 18–226 runs

build_error

glibc

node 18–226 runs

build_error

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

default

✓ import kabaPreset from 'kaba-babel-preset';

✗ const { legacy, modern } = require('kaba-babel-preset');

ESM default export returns an object with `legacy` and `modern` presets. CJS require works but defaults to the object.

legacy

✓ const { legacy } = require('kaba-babel-preset');

✗ import { legacy } from 'kaba-babel-preset';

Named exports are not available as ESM; destructure from default import.

modern

✓ import preset from 'kaba-babel-preset'; const { modern } = preset;

✗ import { modern } from 'kaba-babel-preset';

Use default import then destructure, or CJS destructure.

Shows how to use kaba-babel-preset in a Babel config, selecting legacy or modern preset based on an environment variable.

// babel.config.js module.exports = function (api) { api.cache(true); const { legacy, modern } = require('kaba-babel-preset'); // Example for differential serving based on browser targets const isModern = process.env.BROWSERS_ENV === 'modern'; return isModern ? modern : legacy; };

Debug

Known issues

breakingv4.0.0 changed from a single preset config to returning an object with `legacy` and `modern` presets.

fix

Update usage to destructure the exported object: `const { legacy, modern } = require('kaba-babel-preset');`

affects: >=4.0.0

breakingv3.0.0 switched from individual transforms to `@babel/preset-env`, which may alter polyfilling behavior.

fix

Ensure `core-js` is installed as a peer dependency and configure `useBuiltIns` appropriately.

affects: >=3.0.0

deprecatedThe `loose` mode warning in build output has been removed in v4.1.3, but older versions may produce warnings.

fix

Upgrade to v4.1.3 or later to suppress the warning.

affects: >=4.1.0 <4.1.3

gotchaThe preset expects `core-js` as a peer dependency; missing it will cause polyfill errors at runtime.

fix

Run `npm install core-js@^3.16.1` or add it to your project's dependencies.

affects: >=4.0.0

Errors

Common errors & fixes

Cannot find module 'core-js'

Missing peer dependency `core-js`.

fix

Install core-js: `npm install core-js@^3.16.1`

TypeError: kabaBabelPreset is not a function

Incorrectly assuming the preset is a function; it's an object with properties `legacy` and `modern`.

fix

Use `const { legacy, modern } = require('kaba-babel-preset');`

Error: Multiple presets/plugins with the same name

Duplicate application of kaba-babel-preset due to misconfiguration.

fix

Ensure the preset is only listed once in your Babel config.

Upgrade

Version history

4.1.4latest on npm

Audit

Dependencies

core-jsrequiredpeer dependency for polyfilling via @babel/preset-env's useBuiltIns

Agent activity

2 hits · last 30 days

node

Resources

githubhttps://github.com/Becklyn/kaba-babel-preset ↗

packagehttps://www.npmjs.com/package/kaba-babel-preset ↗