Question 1

How do I enable JavaScript source maps with Smidge?

Accepted Answer

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.

Question 2

Can Smidge handle CSS files from npm packages or node_modules?

Accepted Answer

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.

Question 3

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

Accepted Answer

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.

Question 4

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

Accepted Answer

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.

Question 5

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

Accepted Answer

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.

Question 6

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

Accepted Answer

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.

Smidge

What is Smidge?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions