Skip to main content
AutoprefixerHost package icon

AutoprefixerHost

.NET wrapper around the Andrey Sitnik's Autoprefixer (https://github.com/postcss/autoprefixer) version 10.4.13.0. Since the original library is written in JavaScript, you will need a JS engine to run it. As a JS engine is used the JavaScript Engine Switcher library (https://github.com/Taritsyn/JavaScriptEngineSwitcher). For correct working, you need to install one of the following NuGet packages: * JavaScriptEngineSwitcher.ChakraCore * JavaScriptEngineSwitcher.V8 * JavaScriptEngineSwitcher.Msie (only in the Chakra JsRT modes) 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
325.8K
325,815
Published
Jan 17, 2023
Latest stable version

Install

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

Frameworks

.NETFramework4.0-Client .NETFramework4.5 .NETFramework4.6.1 .NETStandard1.3 net6.0 .NETStandard2.0

Dependencies

AdvancedStringBuilder
.NETFramework4.0-Client
[0.1.0, )
JavaScriptEngineSwitcher.Core
.NETFramework4.0-Client
[3.1.0, )
Newtonsoft.Json
.NETFramework4.0-Client
[13.0.2, )
AdvancedStringBuilder
.NETFramework4.5
[0.1.0, )
[3.1.0, )
Newtonsoft.Json
.NETFramework4.5
[13.0.2, )
AdvancedStringBuilder
.NETFramework4.6.1
[0.1.0, )
[3.1.0, )
System.Text.Json
.NETFramework4.6.1
[4.7.2, )
AdvancedStringBuilder
.NETStandard1.3
[0.1.0, )
[3.1.0, )
NETStandard.Library
.NETStandard1.3
[1.6.1, )
Newtonsoft.Json
.NETStandard1.3
[13.0.2, )
[0.1.0, )
AdvancedStringBuilder
.NETStandard2.0
[0.1.0, )
[3.1.0, )
System.Text.Json
.NETStandard2.0
[4.7.2, )

Adoption guide

Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.

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

Compatibility metadata lists 6 target frameworks; confirm the exact target used by your application.

The published metadata declares 18 direct dependency entries across framework groups. Inspect the resolved dependency graph for your target framework.

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.