Raymond Raymond

ASP.NET Core 2 with Bootstrap 4 Bundler Minifier Issue: Expected semicolon or closing curly-brace found '-'

event 2018-01-23 visibility 3,526 comment 3 insights toc
more_vert
insights Stats

Background

When upgrading Bootstrap to v4.0.0 release, the bundler and minifier doesn’t work properly due to CSS variable is commonly used:

:root{--blue:#007bff;

About 26 errors will show up in the Error List with the following message:

Expected semicolon or closing curly-brace found '-'

image

The environment in my machine has the following setup:

  • VS2017 15.5.4
  • <PackageReference Include="BuildBundlerMinifier" Version="2.6.362" />

Downgrading the package to 2.5.357 doesn't fix the problem in my environment though some people mentioned it can work.

Issue Cause

This issue in BuildBundlerMinifier is caused by another issue in package NUglify:

https://github.com/xoofx/NUglify/issues/17

This issue has not been fixed yet.

It is also raised in GitHub:

https://github.com/madskristensen/BundlerMinifier/issues/295

https://github.com/madskristensen/BundlerMinifier/issues/306

Resolution or Workarounds

Temporary fix

Before this issue is fixed, you can use any of the following approaches to get it work:

  • downgrade your Bootstrap 4 version to beta versions
  • or you change your code temporarily not to minimize bootstrap CSS4 file. You can still bundle and minify your other CSS files which are not using CSS variables.
  • or temporarily manually modify your Bootstrap 4 CSS file to remove that :root section if you are not using bower or other package managers to install those client packages.


I will keep this post updated when the issue is fixed permanently.

More from Kontext
comment Comments
Raymond Raymond #184 access_time 5 years ago more_vert

Hello,

This should has been fixed now according to the issues trackers on GitHub. If you are still encountering this problem, please report to the project site on GitHub.

BTW, I've migrated to use Gulp to package my client resources. Refer to the following page for more details:

Migrate from Bower to Gulp for Client Libraries Management in ASP.NET Core

format_quote

person G Swanson access_time 5 years ago

I am still getting the problem. What do I need to upgrade to fix it?

I am using Visual Studio 2019 and most of my nuget packages are pretty recent.

hide_source Anonymous #49 access_time 5 years ago more_vert

I am still getting the problem. What do I need to upgrade to fix it?

I am using Visual Studio 2019 and most of my nuget packages are pretty recent.

Raymond Raymond #183 access_time 6 years ago more_vert

This issue has now been resolved. 

Please log in or register to comment.

account_circle Log in person_add Register

Log in with external accounts