Skip to content
This repository has been archived by the owner on May 29, 2019. It is now read-only.

[v3.0.0] Load order is broken when used with multiple entry points #573

Closed
tals opened this issue Jul 18, 2017 · 9 comments
Closed

[v3.0.0] Load order is broken when used with multiple entry points #573

tals opened this issue Jul 18, 2017 · 9 comments

Comments

@tals
Copy link

tals commented Jul 18, 2017

Given two entry points that share import-ed modules that extract-text processes, these modules actual load order (as they appear in the concatenated file) will be incorrect

For example:

// programA.js
import './css/first.css'
import './css/second.css'
import './css/third.css'
// programB.js
import './css/second.css'
import './css/first.css'

Yields:

/* extracted programA.css */

/* <content of first.css>... */
/* <content of second.css>... */
/* <content of third.css>... */
/* extracted programB.css */
/* <content of first.css>... <-- this is wrong! */
/* <content of second.css>... */

Repro: https://github.com/tals/extract-text-plugin-ordering-bug

    "extract-text-webpack-plugin": "^3.0.0"
    "webpack": "^3.3.0"

Version in description added by @d3viant0ne

@tals tals changed the title load order is broken with two entry points load order is broken when used with multiple entry points Jul 18, 2017
@michael-ciniawsky
Copy link
Member

Without allChunks: true aswell, did it work before and if what was the latest version it worked correctly?

@michael-ciniawsky michael-ciniawsky changed the title load order is broken when used with multiple entry points [v3.0.0] Load order is broken when used with multiple entry points Jul 19, 2017
@tals
Copy link
Author

tals commented Jul 19, 2017

allChunks makes no difference.

I've only recently started using this plugin, so it never worked for me.
It fails on 2.1.0 and 3.0.0.

@elrumordelaluz
Copy link

elrumordelaluz commented Jul 19, 2017

Don't know if it's related to this issue but upgrading from 2.1.2 into 3.0.0, noted lots of order changes in the output.
Using in both versions allChunks: true and ignoreOrder: true.
Also modules, postcss-loader, postcss-nested and SSR (in case these infos could help).

Commenting in the meantime I am trying to create a repo to reproduce the behaviour

@ciaran-phillips
Copy link

I also have loading order issues which are only present when using multiple entry points. Have not yet tested allChunks but I can confirm I also see the issue on both 2.1.0 and 3.0.0. I'm not sure yet on what version it worked correctly.

@alexander-akait
Copy link
Member

@tals thanks for issue! Can your do PR with failing tests? It help to solve the problem faster

@rkovalov
Copy link

same with 2.1.2

@giotramu
Copy link

giotramu commented Mar 20, 2018

Any update about this Issue? I see the specific branch.

@AndrewBogdanovTSS
Copy link

Any updates regarding this issue?

@alexander-akait
Copy link
Member

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

9 participants