Skip to main content
BundleTransformer.Autoprefixer package icon

BundleTransformer.Autoprefixer

BundleTransformer.Autoprefixer contains one postprocessor-adapter for postprocessing of CSS code - `AutoprefixCssPostProcessor`. This adapter makes actualization of vendor prefixes in CSS code by using the Autoprefixer Host for .NET (https://github.com/Taritsyn/AutoprefixerHost) version 3.0.32 (supports the Andrey Sitnik's Autoprefixer (https://github.com/postcss/autoprefixer) version 10.4.16.1). As a JS engine is used the JavaScript Engine Switcher library (https://github.com/Taritsyn/JavaScriptEngineSwitcher). For correct working of this module, you need to install one of the following NuGet packages: * JavaScriptEngineSwitcher.ChakraCore * JavaScriptEngineSwitcher.Jint * JavaScriptEngineSwitcher.Msie (only in the Chakra JsRT modes) * JavaScriptEngineSwitcher.V8 After installing the packages, you will need to register the default JS engine (https://github.com/Taritsyn/JavaScriptEngineSwitcher/wiki/Registration-of-JS-engines).

Total Downloads
893.9K
893,863
Published
Jan 10, 2024
Latest stable version

Install

.NET CLI
dotnet add package BundleTransformer.Autoprefixer --version 1.13.16
Package Manager Console
Install-Package BundleTransformer.Autoprefixer -Version 1.13.16
PackageReference
<PackageReference Include="BundleTransformer.Autoprefixer" Version="1.13.16" />

Frameworks

.NETFramework4.0

Dependencies

BundleTransformer.Core
.NETFramework4.0
[1.10.0, )
AdvancedStringBuilder
.NETFramework4.0
[0.1.0, )
AutoprefixerHost
.NETFramework4.0
[3.0.32, )
[3.1.0, )

Adoption guide

A verified publisher signal is available. Assess fit from the package's supported frameworks, license and dependency graph rather than popularity alone.

No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.

Compatibility metadata lists 1 target framework; confirm the exact target used by your application.

How to read this guidance

Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.

Useful next steps

Move from package metadata to a concrete selection or review workflow.