-
-
Notifications
You must be signed in to change notification settings - Fork 283
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow from
to be array of paths / glob, respect order
#631
Comments
Respecting order is very bad for perf, work is going on on different cores, please sort them inside |
Hi, I don't see how this would affect performance. The array is already getting sorted ( copy-webpack-plugin/src/index.js Line 648 in beff64e
Only the sorting logic would need te be changed so it does sort according to the input order. |
Because this logic don't know nothing about of input order |
Well, actually it does: copy-webpack-plugin/src/index.js Line 627 in beff64e
item does contain the from property and if from is an array, the sort method has access to the input order.
|
Try to implement this and PR welcome |
I thought you are offering feature requests here? |
I don't understand why you need order by patterns, your order already the same, what is point to do unnecessary calculations |
This feature request basically consists of 2 parts: 1.
|
Yes, we can do it, make sense, but why do not use blog base above and using |
Anyway it is low priority, so PR welcome |
Feature Proposal
Please allow the from property to contain an array of paths / glob patterns
because I need to include files from several different locations and copy them all into one folder.
This is quite ugly and verbose doing it with glob.
The assets array in transformAll should then be returned in the order of the from array so you can rely on javascript execution order.
Feature Use Case
Copying and or concatenating and transforming (javascript) files from multiple locations into one file / folder.
Please paste the results of
npx webpack-cli info
here, and mention other relevant informationnot relevant
The text was updated successfully, but these errors were encountered: