[
https://issues.apache.org/jira/browse/BEAM-12644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17417748#comment-17417748
]
Beam JIRA Bot commented on BEAM-12644:
--------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> JavaScript files are not productionized
> ---------------------------------------
>
> Key: BEAM-12644
> URL: https://issues.apache.org/jira/browse/BEAM-12644
> Project: Beam
> Issue Type: Bug
> Components: website
> Reporter: David Huntsperger
> Priority: P2
> Labels: stale-P2
>
> The custom JavaScript files for the website are not minified, bundled, or
> productionized in any way. They're served with static names, e.g.
> language-switcher.js. As a result, the browser loads cached versions of the
> files, even after we deploy changes. We should minify and bundle the JS
> files, and then deploy them with a GUID in the filename.
>
> Hugo supports [JavaScript building|https://gohugo.io/hugo-pipes/js/], so that
> might provide a solution.
>
> As an alternative fix, we could see if the config on the Cloud Storage bucket
> can be changed in some way to prevent the aggressive caching. The browser
> seems to reload JS files on the staging server, which could indicate a
> difference in config between the staging bucket and prod bucket.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
