drewml / bundlegento Goto Github PK

When bundlegento runs, it operates on the first theme discovered in the specified theme's directory inside pub/static. Every locale needs bundles, but JS should not be changing between locales.

We should do a write operation for the bundles in the first locale, then do a copy (copy-on-write where possible) to the other locales.

bundlegento is the source of knowledge that can answer the question "which bundles should be loaded for X page."

Since Magento does the rendering of the pages, though, bundlegento needs to spit out a manifest mapping layout handle rules >> bundles. The format is documented in MODULESPECS.md

'nuff said

I don't think it's possible to come up with a name that is more cheesy than bundlegento.

Currently, running against luma with m2 sample data, you get an empty cms.js for the homepage.

Requirements
If a group has 0 modules associated with it (after hoisting shared modules):

1. do not output an associated JS bundle file to disk
2. do not add an entry for the bundle in the generated manifest