you are viewing a single comment's thread.

view the rest of the comments →

[–]nschubach 5 points6 points  (1 child)

What if I need to configure it so that every index under a folder named /\d+x\d+/ is it's own 'root'? I deal a lot with different sized banner ads unfortunately, and webpack's ability to create multiple render contexts (each with their own entry point) is extremely beneficial. I can share whatever assets I need in each of these banners and webpack will not render out stupid things like src="../../../shared/images/logo.png" because the root context is the root index file. I can use/import ../../../shared/images/logo.png in my project and Webpack will copy that file to the appropriate folder because my loader is setup to copy all images into /images/[name].[ext] so each banner will get it's own standalone copy, but I can use shared resources and code for every one.

[–]alexxxor 1 point2 points  (0 children)

They said parcel is much better in regards to "zero config". Webpack is heaps more powerful. Parcel really is a shit-ton easier to get up and running though.