How do I enable JavaScript source maps with Smidge?

Source maps are supported via the Smidge.Nuglify package. Install it separately and configure the pipeline to include source map generation during minification, as mentioned in the features section.

Can Smidge handle CSS files from npm packages or node_modules?

Smidge can process any CSS or JS file referenced in your project, but integrating npm packages may require manual file inclusion or custom processors to resolve paths, as it focuses on runtime processing within ASP.NET Core.

Smidge vs Microsoft's built-in bundling in ASP.NET Core: which is better?

Smidge offers more features like runtime processing, extensibility, and robust caching, while built-in bundling is simpler but less powerful. Smidge is better for projects needing advanced asset management without external build tools.

How to add a custom pre-processor for a new file type in Smidge?

Implement a custom processor by extending Smidge's pipeline and register it in the configuration. The documentation provides examples for extending the pre-processing workflow, though it's noted as incomplete.

Does Smidge support cache busting with query strings or file hashes?

Yes, Smidge includes customizable cache busting mechanisms that can use query strings or other methods, and you can replace or customize how it works to ensure clients fetch updated bundles.

What's the impact of using Smidge on application startup time?

Initial bundle processing might slow startup slightly, but persistent server-side caching minimizes this after the first request. In production, pre-warming caches or tuning settings can help mitigate delays.

Open-Awesome

Smidge

MITC#v5.0.0

A lightweight runtime CSS/JavaScript minification, bundling, and management library for ASP.NET Core.

GitHub

371 stars49 forks0 contributors

What is Smidge?

Smidge is a runtime asset processing library for ASP.NET Core that minifies, combines, compresses, and manages CSS and JavaScript files. It solves the problem of optimizing web assets at runtime with built-in caching, cache busting, and extensible pipelines. Developers use it to improve frontend performance without relying on complex build tools.

Target Audience

ASP.NET Core developers who need lightweight runtime asset bundling and minification without external build tools. It's ideal for projects where simplicity and integration with the ASP.NET Core pipeline are priorities.

Value Proposition

Smidge offers a native, extensible, and developer-friendly alternative to build-time bundlers, with seamless ASP.NET Core integration, a fluent configuration API, and robust caching mechanisms. Its runtime processing eliminates the need for separate build steps while providing production-ready optimizations.

Overview

A lightweight runtime CSS/JavaScript file minification, combination, compression & management library for ASP.Net Core

Use Cases

Best For

Adding runtime JavaScript and CSS minification to ASP.NET Core applications
Creating configurable asset bundles with environment-specific settings
Implementing cache busting and client-side caching for static assets
Extending asset processing pipelines with custom processors
Integrating source maps for minified JavaScript files
Using tag helpers to render bundles directly in Razor views

Not Ideal For

Projects using modern frontend frameworks with comprehensive build tools like Webpack or Vite
High-traffic applications where runtime asset processing could introduce unacceptable server load
Teams requiring out-of-the-box support for CSS preprocessors like Sass or LESS without custom development

Pros & Cons

Pros

Seamless ASP.NET Integration

Integrates natively with ASP.NET Core services and tag helpers, enabling easy setup and rendering in Razor views without external tools, as shown in the quick start guide.

Flexible Bundle Configuration

Offers a fluent API for defining bundles with environment-specific settings and file watchers, allowing precise control over asset processing in debug or production modes.

Robust Caching System

Implements persistent server-side caching and properly configured client-side caching with cache busting, reducing unnecessary rebundling and improving performance.

Extensible Processing Pipeline

Supports complete customization of pre-processor pipelines and custom processors for any file type, as highlighted in the features for extensibility.

Cons

Documentation Gaps

The README admits that not all features are documented yet, which can make advanced configuration and troubleshooting challenging for new users.

Runtime Performance Cost

Processing assets at runtime adds server overhead compared to pre-compiled bundles, potentially affecting scalability in high-demand scenarios.

Additional Dependencies Needed

Advanced features like JavaScript source maps require installing separate packages (e.g., Smidge.Nuglify), increasing dependency management complexity.

Frequently Asked Questions

Related Projects

BundlerMinifier

Visual Studio extension

Stars626

Forks180

Last commit2 years ago

Web Markup Minifier

The Web Markup Minifier (abbreviated WebMarkupMin) - a .NET library that contains a set of markup minifiers. The objective of this project is to improve the performance of web applications by reducing the size of HTML, XHTML and XML code.

An ASP.NET MVC ViewEngine for rendering markup in a JavaScript environment. Ideal for React and Angular server-side rendering.

Stars72

Forks14

Last commit8 years ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub