How do I use parcelify with SCSS files?

Install a transform like sass-css-stream and specify it in your package.json 'transforms' field or use the -t flag with parcelify. This allows SCSS files to be automatically converted to CSS during bundling.

parcelify vs webpack css loader: which is better?

Parcelify is specific to browserify and treats CSS as npm dependencies, ideal for modular projects. Webpack's css-loader is part of a broader ecosystem with more features like CSS modules and better integration with modern frameworks.

Can parcelify handle multiple CSS bundles for different entry points?

Yes, use the 'bundlesByEntryPoint' option in the API to map entry points to separate CSS bundles, as shown in the README example for multi-entry applications.

Why is parcelify's command line usage deprecated?

The README states CLI usage is depreciated to encourage use as a browserify plugin, focusing on integration rather than standalone operation, which may affect ease of use in some workflows.

How to set up watch mode with parcelify in development?

Use the -w flag with watchify and parcelify, e.g., 'watchify main.js -o bundle.js -p [ parcelify -wo bundle.css ]' to automatically rebuild CSS on file changes.

Does parcelify support CSS modules or PostCSS?

Not natively; you'd need custom transforms or additional tools. Parcelify focuses on bundling raw or preprocessed CSS from npm modules, so advanced CSS features require extra configuration.

parcelify — CSS Bundler for Browserify

What is parcelify?

Parcelify is a browserify plugin that enables npm modules to include and bundle CSS assets alongside JavaScript code. It solves the problem of managing CSS dependencies in modular frontend projects by allowing packages to declare CSS files in their package.json, which are then concatenated in dependency order.

Target Audience

Frontend developers using browserify who need to manage CSS dependencies across npm modules, particularly those building modular UI components or shared design systems.

Value Proposition

Developers choose Parcelify because it integrates CSS bundling directly into the browserify workflow, treating styles as versioned dependencies rather than global assets. Its transform system supports preprocessors, and its watch mode streamlines development.

Add css to your npm modules consumed with browserify.

Use Cases

Best For

Bundling CSS from npm modules in browserify-based projects
Managing CSS dependencies for modular UI component libraries
Preprocessing SCSS or Less files within npm packages
Automatically rebuilding CSS during development with watch mode
Building larger asset management tools on top of browserify
Handling CSS for multi-entry point applications with separate bundles

Not Ideal For

Projects using modern bundlers like webpack, rollup, or Vite instead of browserify
Teams adopting CSS-in-JS solutions such as styled-components or emotion for scoped styles
Applications requiring built-in CSS modules or PostCSS processing without additional configuration
Developers seeking an all-in-one build tool with integrated CSS handling, like Parcel or esbuild

Pros & Cons

Pros

CSS as Dependencies

Packages declare CSS files in the 'style' field of package.json, enabling versioned and shared styles across npm modules, as shown in the example with glob notation.

Preprocessor Integration

Supports transforms like sass-css-stream and less-css-stream for efficient preprocessing of SCSS and Less files within packages, reducing build complexity.

Development Watch Mode

Automatically rebuilds CSS bundles when source files change using the -w flag, streamlining development workflows with browserify's watchify.

Flexible API for Extensions

Provides a robust API that supports arbitrary asset types and enables building larger tools like cartero, as mentioned in the README.

Cons

Browserify Dependency

Only works with browserify, making it incompatible with other popular bundlers and locking projects into a specific ecosystem.

Deprecated CLI Functionality

Command-line usage is marked as deprecated, indicating potential maintenance issues and reduced long-term support for standalone use.

Limited Modern CSS Features

Focuses on traditional CSS files and preprocessors, lacking native support for CSS-in-JS or modern CSS modules without complex transform setups.

Complex Advanced Configuration

Setting up multiple entry points or custom transforms requires careful API configuration, which can be cumbersome for simple projects compared to integrated tools.

Frequently Asked Questions

What is parcelify?

Target Audience

Frontend developers using browserify who need to manage CSS dependencies across npm modules, particularly those building modular UI components or shared design systems.

Value Proposition

Use Cases

Best For

Bundling CSS from npm modules in browserify-based projects
Managing CSS dependencies for modular UI component libraries
Preprocessing SCSS or Less files within npm packages
Automatically rebuilding CSS during development with watch mode
Building larger asset management tools on top of browserify
Handling CSS for multi-entry point applications with separate bundles

Not Ideal For

Projects using modern bundlers like webpack, rollup, or Vite instead of browserify
Teams adopting CSS-in-JS solutions such as styled-components or emotion for scoped styles
Applications requiring built-in CSS modules or PostCSS processing without additional configuration
Developers seeking an all-in-one build tool with integrated CSS handling, like Parcel or esbuild

Pros & Cons

Pros

CSS as Dependencies

Packages declare CSS files in the 'style' field of package.json, enabling versioned and shared styles across npm modules, as shown in the example with glob notation.

Preprocessor Integration

Supports transforms like sass-css-stream and less-css-stream for efficient preprocessing of SCSS and Less files within packages, reducing build complexity.

Development Watch Mode

Automatically rebuilds CSS bundles when source files change using the -w flag, streamlining development workflows with browserify's watchify.

Flexible API for Extensions

Provides a robust API that supports arbitrary asset types and enables building larger tools like cartero, as mentioned in the README.

Cons

Browserify Dependency

Only works with browserify, making it incompatible with other popular bundlers and locking projects into a specific ecosystem.

Deprecated CLI Functionality

Command-line usage is marked as deprecated, indicating potential maintenance issues and reduced long-term support for standalone use.

Limited Modern CSS Features

Focuses on traditional CSS files and preprocessors, lacking native support for CSS-in-JS or modern CSS modules without complex transform setups.

Complex Advanced Configuration

Setting up multiple entry points or custom transforms requires careful API configuration, which can be cumbersome for simple projects compared to integrated tools.

Frequently Asked Questions

parcelify

What is parcelify?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?

parcelify

What is parcelify?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?