Hashes wrong (cache?) in production - ideas why?

[nystudio107]

Hashes wrong (cache?) in production - ideas why?

[bryandugan]

Did you clear the cache in the Craft CP at Utilities > Clear Caches > Twigpack Manifest Cache?

I was just having the same issue and that fixed it for me on my production site.

Andrew also has a script that he uses to clear the cache on every deploy if that's helpful. https://nystudio107.com/docs/twigpack/#caching

Here is the way I also include Twigpack in my layouts if that's helpful.

Header

    {{ craft.twigpack.includeCssModule("app.css", true) }}

    {% if getenv('ENVIRONMENT') != 'dev' and getenv('ENVIRONMENT') != 'local' %}
        {{ craft.twigpack.includeCssModule("app.css") }}
    {% endif %}

Footer

{{ craft.twigpack.includeSafariNomoduleFix() }}
{{ craft.twigpack.includeJsModule("chunk-vendors.js", true) }}
{{ craft.twigpack.includeJsModule("app.js", true) }}

If it's none of that, then it may quite possibly be an issue with the shared hosting setup.

[janeschindler]

Thanks for looking at this. Yes, I cleared all caches many times. It's a good idea to find out more about hosting. I don't know that much about server setups. What do you suspect could be a problem? It would be good to have more info before I call up the host.
-> Also, it would be good to know what kinds of disadvantages there might be to linking the CSS and JS without hashes, since that appears to be working right now. What is the reason for the hashes in the first place? Why does my app work fine without them?
Thanks.

[khalwat]

Hashes are there to ensure that when files change, the clients won't be using an outdated version of the scripts/CSS.

See here for more: https://webpack.js.org/guides/caching/