Registry / devops / pacco
library0.4.3jsnpmunverified

Pacco is a JavaScript bundler designed for modular and extensible web projects, focusing on building client-side assets like JavaScript and SCSS. Currently at version 2.1.18, its development appears to be inactive; the last update was in November 2021, and its documentation explicitly states it is a 'TODO' dependent on user interest. This tool distinguishes itself from alternatives like Webpack by offering zero-configuration setup, supporting partial builds to compile only necessary files, and providing extensibility features for injecting or overriding files. It also allows for module priority configuration, ensuring critical code loads early for improved perceived performance. Pacco is built on top of Gulp, enabling easy integration with existing Gulp-based build systems and facilitating further customization with Gulp plugins. However, its maintenance status and lack of comprehensive documentation make it a less viable option for new projects compared to actively developed bundlers.

npm install pacco
INSTALL
IMPORT
SIG · PACCO
P
pacco
devopsjavascriptv0.4.3
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.

pacco
const pacco = require('pacco');
import pacco from 'pacco';
Pacco is primarily used within a Gulpfile.js, leveraging CommonJS `require()` syntax for integration. It does not provide named or default ESM exports for direct application-level imports.

Demonstrates how to integrate Pacco into a basic Gulpfile.js to perform a build task, assuming Pacco functions as a Gulp plugin for bundling.

const gulp = require('gulp'); const pacco = require('pacco'); // A minimal Gulp task to demonstrate Pacco usage. // In a real project, 'pacco' would be configured with options // for source directories, output, and specific build configurations. // Given the lack of documentation, specific options are not provided. gulp.task('build-pacco', function() { console.log('Running Pacco build...'); // This is a placeholder. Actual Pacco configuration would go here. // Based on the README, it 'just works' without explicit config, // implying it might infer inputs/outputs or use a default CLI approach. // If used as a Gulp plugin, it would likely take a stream or config object. // Example placeholder for demonstration purposes: return gulp.src('./src/**/*.js') // Or specific entry points .pipe(pacco.bundle({ /* options based on project structure */ })) .pipe(gulp.dest('./dist')); }); gulp.task('default', gulp.series('build-pacco')); // To run: // 1. Install gulp-cli globally: npm install -g gulp-cli // 2. Install gulp and pacco locally: npm install gulp pacco --save-dev // 3. Create a 'gulpfile.js' in your project root with the above content. // 4. Create a 'src' directory and add some '.js' files. // 5. Run 'gulp build-pacco' or just 'gulp' in your terminal.
pacco --version
Debug
Known issues
gotchaPacco lacks comprehensive official documentation. The project's README explicitly states documentation is a 'TODO' item dependent on community interest, making it challenging to learn and troubleshoot without diving into the source code or the associated Svelto framework's codebase.
fix
Review the `svelto` framework's source code (the project Pacco was built for) for usage patterns. Be prepared for reverse-engineering or relying on outdated examples.
affects: >=1.0.0
breakingThe Pacco project appears to be largely unmaintained. The last update on npm was in November 2021, and the GitHub repository shows limited recent activity. This suggests a lack of ongoing bug fixes, security updates, or feature development, making it unsuitable for new projects or environments requiring active support.
fix
Consider using actively maintained and well-documented bundlers like Webpack, Rollup, or Parcel for new projects. If using Pacco for a legacy project, be aware of potential compatibility issues with newer Node.js versions or ecosystem changes.
affects: >=2.0.0
gotchaPacco's architecture, being developed before Webpack became dominant and built on Gulp, may not align with modern JavaScript module bundling practices or support advanced features found in contemporary bundlers. It might lack out-of-the-box support for modern language features, tree-shaking, or advanced optimization techniques.
fix
For projects requiring modern bundling capabilities, evaluate alternative bundlers. If bound to Pacco, be prepared to implement custom Gulp tasks or extend Pacco's functionality to achieve desired outcomes, which may be complex due to limited documentation.
affects: >=1.0.0
Upgrade
Version history
0.4.3latest on npm
Audit
Dependencies
gulprequiredPacco is built on top of Gulp and is integrated as a Gulp task. It requires Gulp to be installed as a peer dependency in the consuming project's development environment.
Agent activity
2 hits · last 30 days
node
2
Resources
pacco — npm install pacco · libregistry