get wrong css order after using HashedModuleIdsPlugin

[silaike]

Do you want to request a feature or report a bug?
Bug.

What is the current behavior?
get wrong css order after using HashedModuleIdsPlugin

If the current behavior is a bug, please provide the steps to reproduce.
webpack plugin configs.

       ...
	plugins: [
		new HtmlWebpackPlugin( {
			filename: 'index.html',
			template: 'index.ejs',
			minify: {
				collapseWhitespace: true,
				minifyJS: true
			}
		} ),

		new ExtractTextPlugin( {
			filename: 'css/[name].[contenthash:8].css',
			allChunks: true,
		} ),

		new OptimizeCssAssetsPlugin( {
			cssProcessor: require( 'cssnano' ),
			cssProcessorOptions: {
				autoprefixer: false
			}
		} ),

		new webpack.HashedModuleIdsPlugin(),

		new webpack.optimize.CommonsChunkPlugin( {
			names: [ 'vendor', 'manifest' ],
		} ),

		new webpack.optimize.CommonsChunkPlugin( {
			async: 'async-common',
			minChunks: ( module, count ) => (
				count >= 2
			),
		} ),

		new webpack.DefinePlugin( {
			'process.env': {
				NODE_ENV: JSON.stringify( 'production' )
			}
		} ),

		new webpack.optimize.UglifyJsPlugin( {
			compress: {
				warnings: false
			},
			comments: false
		} ),

		new webpack.optimize.ModuleConcatenationPlugin(),
	]

What is the expected behavior?
remove HashedModuleIdsPlugin then css order will be right.

Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
webpack version v3.6.0

[sgal]

Same issue with NamedModulesPlugin. Fails on v3.5.1 as well.
Might be related to webpack-contrib/extract-text-webpack-plugin#601

[Kubaka1]

Same issue +1... @sokra can help this?

[cletusw]

Likely fix merged: d5a1de21a65532f66b05a1f6c2146574ce385567

[alexander-akait]

@webpack-bot move to webpack-contrib/extract-text-webpack-plugin

Failed test webpack-contrib/extract-text-webpack-plugin#710

[webpack-bot]

I've moved it to webpack-contrib/extract-text-webpack-plugin.