You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AMP Optimizer usually runs either at build time or at runtime. Both modes have very different constraints in regards to execution time:
Runtime: AMP Optimizer is executed in the critical rendering path requiring minimal execution times.
Build time: AMP Optimizer is used at build time (e.g. for static sites). In this case, execution time is less critical enabling more expensive optimizations.
Steps we should take to better support this:
Provide two different out-of-the box configurations for runtime and build time usage (see Add minimal Optimizer Transformer Config #1180 for a start). The runtime config should only perform AMP specific server-side optimizations, but avoid any expensive optimizations such as minification.
Improve default install times by making all non-essential dependencies (cssnano-simple, postcss, terser) optional.
The text was updated successfully, but these errors were encountered:
AMP Optimizer usually runs either at build time or at runtime. Both modes have very different constraints in regards to execution time:
Steps we should take to better support this:
The text was updated successfully, but these errors were encountered: