Currently supporting ASP.NET Core 1.0, built against NETStandard.1.6 & .Net Framework 4.5.2
Install-Package Smidge -Pre
//Then register/configure smidge services services.AddSmidge(/* optional IConfiguration parameter */);
See Installation for full configuration details
Define your bundles during startup:
If you don't want to create named bundles and just want to declare dependencies individually inside your Views, you can do that too! You can create bundles (named or unnamed) during runtime ... no problem.
See Declarations for full declaration/usage details
The easiest way to render bundles is simply by the bundle name:
This uses Smidge's custom tag helpers to check if the source is a bundle reference and will output the correct bundle URL. You can combine this with environment variables for debug/non-debug modes. Alternatively, you can also use Razor to do the rendering.
See Rendering for full rendering & debug mode details
Custom pre-processing pipeline
It's easy to customize how your files are processed including the way files are minified, how URLs are resolved, etc.... This can be done at a global/default level, at the bundle level or at an individual file level.
See Custom Pre-Processing Pipeline for information about customizing the pre-process pipeline
There's a couple of methods you can use retrieve the URLs that Smidge will generate when rendering the
<script> html tags. This might be handy in case you need to load in these assets manually (i.e. lazy load scripts, etc...):
Task<IEnumerable<string>> SmidgeHelper.GenerateJsUrlsAsync() Task<IEnumerable<string>> SmidgeHelper.GenerateCssUrlsAsync()
See Asset URLs for information about retrieving the debug and non-debug asset urls for your bundles
I haven't had time to document all of the features and extensibility points just yet but I'm working on it :)
Copyright & Licence
© 2016 by Shannon Deminick
This is free software and is licensed under the MIT License
Logo image Designed by Freepik