Please provide the output of ng --version.
A minimal reproduction would also be very useful to aid in further investigate of the issue.

ng --version:

Your global Angular CLI version (1.6.7) is greater than your local
version (1.6.5). The local Angular CLI version is used.

To disable this warning use "ng set --global warnings.versionMismatch=false".

    _                      _                 ____ _     ___
   / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
  / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
 / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
/_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
               |___/
    
Angular CLI: 1.6.5
Node: 9.4.0
OS: linux x64
Angular: 4.4.6
... animations, common, compiler, compiler-cli, core, forms
... http, platform-browser, platform-browser-dynamic
... platform-server, router, tsc-wrapped

@angular/cli: 1.6.5
@angular-devkit/build-optimizer: 0.0.42
@angular-devkit/core: 0.0.29
@angular-devkit/schematics: 0.0.52
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.9.5
@schematics/angular: 0.1.17
typescript: 2.4.2
webpack: 3.10.0

When I open xxxxbundle.css I find the order of css injections different than the order specified in angular-cli.json

I have the same issue starting cli 1.6.4 (does not occurs on 1.7.0-beta3).

I can confirm this issue exists in angular-cli 1.65, 1.6.6 and 1.6.7. If you reverse the order of your styles array in angular-cli.json, you can preview the bug in 'serve' mode, to a degree

@clydin on 1.6.7, when I build with a styles array like below:

  "styles": [
    "../node_modules/bootstrap/dist/css/bootstrap.min.css",
    "../node_modules/font-awesome/css/font-awesome.min.css",
    "../node_modules/angular-calendar/dist/css/angular-calendar.css",
    "../node_modules/nouislider/distribute/nouislider.min.css",
    "styles.scss"
  ],

The CSS files are bundled with styles.scss at the top. The rest follow the correct order. (In my screenshoot, nouislider is after angular-calendar on the same line; it's in there, but not in the screenshot).

Reverting to 1.6.3 (and then installing @angular-devkit/core@0.0.29 manually via NPM) was the only solution I could find.

ng build --prod -extract-css false solved the problem until finding final solution

@clydin I'm experiencing this issue with the Angular CLI v1.7.1 too. The styles array looks like this:

"styles": [
    "./app/shared/styles/material-theming.css",
    "./app/shared/styles/styles.css"
],

Yet, the CSS of material-theming.css is inserted below the rules of styles.css.

This issue is marked with the label "need: more info". What other info can we provide that would help you debug this?

I had the same problem while adding third-party CSS framework I wanted to extend. Finaly I just imported it through src/styles.(sass/css/scss) and it works great. As styles you insert into .angular-cli.json are intended to be global, using src/styles.(sass/css/scss) you reach the same goal. I think it's a nice work around.

I had the same problem with 1.6.4 and switching to cli 1.7.4 fixed it.

Did a clean npm i with the latest everything, including cli 1.7.4 — the problem is still there.

I’m afraid “need: more info” label diverts attention away from this issue while ng --version was provided back in February.

Strangely, I notice that the styles are in the desired order when I run in dev mode, but in the wrong order when I run in production.

Any update on this?

@andresmgsl Not sure which version fixed this, but it's not present in 1.7.1, at least.

I already reverted CLI twice because of this issue.

1.71 > 1.68
1.74 > 1.68

Same problem with 6.03 version now.

Dev build is fine, prod build still not good.

Related: #10579

I solved this issue by placing the css I wanted to import on top of styles.css instead of in the json file like recomended...

This issue is still present in 6.0.5. Or at least in some form. I'm migrating an existing project to Angular CLI, and when disabling extractCss, it works as intended, while with extractCss enabled, the styles are broken.

@nicolasfoisy can you please explain what you did there to solve it?
what do you by placing the css... where did you place it? copied it into styles.css?

Still present in 6.0.7. Setting extractCss to false fixes it for me too.

Indeed issue is still present:

Repo: https://github.com/ErazerBrecht/ErazerCQRS/blob/5861a00cd484bc689d41212de248e46ba8d8a891/Erazer.Web.Angular/angular.json#L23

styles.css is the last style in the array but when extractCss is enabled, the bootstrap css file overwrites the styles.css rules because it's added under it in the bundle.

Angular CLI: 6.0.8
Node: 10.4.0
OS: win32 x64
Angular: 6.0.4

@ErazerBrecht I am using a .scss file with the imports of the third party style instead of the style.css and I am having the same issue, every time I run the command ng build --prod it create the dist folder but the style.css is like corrupted because all classes are together in 1 line and are not taking effect, same happens to the main.js file.😓😭

do you think I should change it back to the style.css?

@clydin I also see a similar problem, but I build my application with custom webpack config. And CSS selectors is reorder when I have AngularCompilerPlugin in my pipeline.

I'm created repository for showing this problem. In it you will see 2 directories (dist-dev and dist-prod) with different ordering CSS selectors.

I'm using:

Angular CLI: 6.0.8
Node: 9.10.1
OS: MacOS 10.13.4
Angular: 6.0.9

It turned out to fix the problem by transferring the import common.scss from the app.module.ts to the browser.module.ts. But I'm sure that this is really the right decision.

I'm uploaded this fix in fix-reorder branch

Anyone else have a workaround for this issue? Setting extractCss doesn't seem to work for me either... Angular CLI 6.1.5.

@Trojaan i fixed this issue with this
issue #13948
adding this line in the index
<script>document.write('<base href="' + document.location + '" />');</script>
angular/angular#13948

@oneal1801 Thanks! This fixed it! :)

Very strange bug. My temporary solution:

moved all css files from angular.json to styles.scss using @import

Any update on this bug.
I face the same issue. I did the same workaround as fedotxxl but this is not the proper way and I receive depreciation warning:
"Including .css files with @import is non-standard behaviour which will be removed in future versions of LibSass.
Use a custom importer to maintain this behaviour. Check your implementations documentation on how to create a custom importer."

Thanks for the feedback

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}