You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Irwin Alejandro Rodirguez Ramirez (Jira)" <ji...@apache.org> on 2021/10/01 18:08:00 UTC

[jira] [Assigned] (BEAM-12644) JavaScript files are not productionized

     [ https://issues.apache.org/jira/browse/BEAM-12644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Irwin Alejandro Rodirguez Ramirez reassigned BEAM-12644:
--------------------------------------------------------

    Assignee: Irwin Alejandro Rodirguez Ramirez

> 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
>            Assignee: Irwin Alejandro Rodirguez Ramirez
>            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)