Write AMP_CONFIG to 3p frame to enable local development #12703
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR causes
gulp | gulp watch | gulp build | gulp dist --fortesting
to writeAMP_CONFIG
to the 3p frame target file in addition to the AMP runtime file. This enables testing with non-localhost servers.In addition, now that we're writing
AMP_CONFIG
by default to the runtime file and the 3p frame file, we can simplify the heroku setup scripts to no longer have to invokegulp prepend-global
.For context, see #12054 (comment)
Follow up to #12673
Unblocks #12666
Fixes #12054