You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When declaring the below scss bundle pipe.AddScssBundle("/css/site.bundle.css", "/lib/jqueryui/jquery-ui.min.css", "/lib/bootstrap/scss/bootstrap.scss");
then disabling enableTagHelperBundling in appsettings.json "enableTagHelperBundling": false
it gets rendered as bootstrap.css, not bootstrap.scss <link href="/lib/jqueryui/jquery-ui.min.css?v=rByPlHULObEjJ6XQxW_flG2r-22R5dKiAoef-aXWfik" rel="stylesheet"> <link href="/lib/bootstrap/scss/bootstrap.css" rel="stylesheet">
In my case "/lib/bootstrap/scss/bootstrap.css" does not exist, therefore the browser throws a 404 not found.
Any ideas?
The text was updated successfully, but these errors were encountered:
I have found this closed issue (ligershark/WebOptimizer.Sass#2) and I can see that the code was explicitly altered to change extension from .scss to .css. This was done in commit 6ae221a (Code below)
IMO, enableTagHelperBundling should load the css bundles so the browser works or the scss with the mapping.
The pages fail because we would have to reference each scss file accordingly on the page. Shouldn't enableTagHelperBundling work like Typescript vs Javascript mapping? Browser runs the javascript but makes the Typescript visible to debug with.
Hi,
When declaring the below scss bundle
pipe.AddScssBundle("/css/site.bundle.css", "/lib/jqueryui/jquery-ui.min.css", "/lib/bootstrap/scss/bootstrap.scss");
then disabling enableTagHelperBundling in appsettings.json
"enableTagHelperBundling": false
it gets rendered as bootstrap.css, not bootstrap.scss
<link href="/lib/jqueryui/jquery-ui.min.css?v=rByPlHULObEjJ6XQxW_flG2r-22R5dKiAoef-aXWfik" rel="stylesheet">
<link href="/lib/bootstrap/scss/bootstrap.css" rel="stylesheet">
In my case "/lib/bootstrap/scss/bootstrap.css" does not exist, therefore the browser throws a 404 not found.
Any ideas?
The text was updated successfully, but these errors were encountered: