-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add script to header to load javascript runtime #1841
base: main
Are you sure you want to change the base?
Conversation
Can you confirm that you've verified whether there's any impact to the injected header? How to test: https://github.com/department-of-veterans-affairs/vets-website/tree/main/src/applications/proxy-rewrite |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
This PR is stale because it has been open 120 days with no activity. It will receive a stale label every day for 14 days before being closed unless it receives a comment or the stale label is removed. |
Review instance with this branch + vets-website #27559 is available here: http://b7ae1dc6cd3e30dd6b86a7ed15ceb26a.review.vetsgov-internal/ The build completed successfully:
The runtime file is available here: http://b7ae1dc6cd3e30dd6b86a7ed15ceb26a.review.vetsgov-internal/generated/runtime.entry.js The header, megamenu, footer and various applications all load and work correctly. |
Summary
This is a companion PR to this
vets-website
PR, which updates thevets-website
webpack config to reduce bundle size. Part of this webpack change results in the extraction of the webpack runtime from each bundle. To make the bundles work in va.gov, therefore, a new script tag must be added to the<head>
tag where the runtime is downloaded.Related issue(s)
department-of-veterans-affairs/vets-website#27559
Testing done
Testing doc is here.
Screenshots
There should be no visual change due to this change.
Before:
After:
Acceptance criteria
Quality Assurance & Testing
Error Handling
Authentication
#sitewide-public-websites
Slack channel for questionsRequested Feedback
(OPTIONAL) What should the reviewers know in addition to the above. Is there anything specific you wish the reviewer to assist with. Do you have any concerns with this PR, why?