We're a large, slow-moving, process-change-aversion, oss-scared
organization. And unfortunately, because of our schedule, this isn't
the time to try and accomplish this if it's not plug-n-play. And
from what I've read, with our setup, there's going to be lots of
moving parts.
But, here are a few of my concerns:
Right now, with "old steal", we have the development and production (steal-built) versions running pretty smoothly. We have cache-busting implemented in our production builds and everything works fine (except for our IE bug). From reading the docs/forums, I couldn't readily figure out if true cache-busting (filename-changing [e.g., production.js -> production.1234123423.js], not version adding [?v1]) was even supported--seemed like the "was coming".
The migration guide talked about making changes in the stealconfig.js settings but it was never really apparent that we could keep our stealconfig.js setup and just plug in the new stealJS. Our dev and prod versions have different setups so that we can use dev and prod versions of all the plugins we use as well. For dev buillds it uses stealconfig.js in the base directory, for production it ignores stealconfig.js and index.html contains a steal object that maps the production (minified) versions of the libraries/plugins. Is this still doable with new stealJS?
But, here are a few of my concerns:
Right now, with "old steal", we have the development and production (steal-built) versions running pretty smoothly. We have cache-busting implemented in our production builds and everything works fine (except for our IE bug). From reading the docs/forums, I couldn't readily figure out if true cache-busting (filename-changing [e.g., production.js -> production.1234123423.js], not version adding [?v1]) was even supported--seemed like the "was coming".
The migration guide talked about making changes in the stealconfig.js settings but it was never really apparent that we could keep our stealconfig.js setup and just plug in the new stealJS. Our dev and prod versions have different setups so that we can use dev and prod versions of all the plugins we use as well. For dev buillds it uses stealconfig.js in the base directory, for production it ignores stealconfig.js and index.html contains a steal object that maps the production (minified) versions of the libraries/plugins. Is this still doable with new stealJS?