Registry / devops / pakit
library0.2.5jsnpmunverified

pakit is an opinionated JavaScript bundler (v2.3.0) that provides out-of-the-box linting, transpilation, minification, and sourcemaps with minimal configuration. It supports CommonJS and ES2015 modules, bundle splitting via shards, file watching, caching, and configuration through .pakit.json, .pakit.js, or .pakit directory. Integrates with eslint, babel, and uglify, respecting their rc files for non-invasiveness. Differentiated by its strong defaults and modular configuration approach. Release cadence is sporadic; latest stable is v2.3.0.

npm install pakit
INSTALL
IMPORT
SIG · PAKIT
P
pakit
devopsjavascriptv0.2.5
Install
Import
Disk
Pass rate
0/ 6
Env Coverage0 / 6
glibc
1822
musl
1822
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 18226 runs
build_error
glibc
node 18226 runs
build_error
Code
Verified usage

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

pakit
import pakit from 'pakit'
const pakit = require('pakit')
pakit is a default export, but CommonJS also works. ESM import recommended for bundling.
pakit
const pakit = require('pakit')
import { pakit } from 'pakit'
pakit is a default export; named import syntax is incorrect.
Bundle
import { Bundle } from 'pakit'
import Bundle from 'pakit'
Bundle is a named export, not default. Use named import syntax.

Demonstrates programmatic usage of pakit with entry files, output path, minification, sourcemaps, and bundle splitting into vendor shard.

import pakit from 'pakit'; import path from 'path'; pakit({ entries: ['./src/index.js'], out: path.resolve('dist/bundle.js'), watch: false, minify: true, sourcemap: true, shards: { 'dist/vendor.js': ['/node_modules/'] } }).then(result => { console.log('Build succeeded:', result); }).catch(err => { console.error('Build failed:', err); });
pakit --version
Debug
Known issues
deprecated.bundlerrc configuration files are deprecated. Please rename to .pakit file.
fix
Rename .bundlerrc to .pakit.json, .pakit.js, or .pakit directory.
affects: >=0.6.2
breakingIn v0.6.0, bundlerrc support was removed without warning. Recovery release v0.6.2 added deprecation warning.
fix
Upgrade to v0.6.2 or later. Rename .bundlerrc to .pakit.
affects: 0.6.0 - 0.6.1
gotchaESLint config detection uses glob for .eslintrc files; ensure your config file is named correctly (e.g., .eslintrc.json).
fix
Use a supported .eslintrc file (json, js, yaml) in project root.
affects: >=0.6.1
gotchaBundle splitting shard matchers are internally converted to regular expressions. Escape special characters if matching literal strings.
fix
Use proper regex escaping in shard match patterns.
affects: >=0.5.0
Errors
Common errors & fixes
Error: Cannot find module 'eslint'
eslint is not installed when using pakit, but required for linting.
fix
Install eslint as a dev dependency: npm install eslint --save-dev
Error: Could not find configuration file .pakit.json, .pakit.js, or .pakit directory
pakit cannot find any configuration file in the project root.
fix
Create a .pakit.json file or use the programmatic API with explicit options.
TypeError: pakit is not a function
Misimporting pakit (e.g., using named import instead of default).
fix
Use import pakit from 'pakit' or const pakit = require('pakit').
Unexpected token: keyword «import»
pakit requires babel to transpile ES6 modules if using .babelrc; if not configured, babel may not be active.
fix
Ensure babel-core is installed and .babelrc is present, or use CommonJS require syntax.
Upgrade
Version history
0.2.5latest on npm
Audit
Dependencies
eslintoptionalLinting support
babel-coreoptionalJavaScript transpilation
uglify-jsoptionalMinification
Agent activity
2 hits · last 30 days
node
2
Resources
pakit — npm install pakit · libregistry