Sylius: Stale asset cache in the browser between Sylius upgrades

[mikemix]

Describe the proposed solution
If you update Sylius version, new assets are built, but client browser cache does not refresh that easily and still uses previous assets (css files etc.). Do you have any easy solution for this?

Describe alternatives you've considered
Override template, generate manifest file for assets, include assets by myself.

Additional context
None.

[pamil]

As @teohhanhui mentioned on Sylius' Slack:

we need to use one of version, version_strategy or json_manifest_path
https://symfony.com/doc/current/reference/configuration/framework.html#version

[teohhanhui]

This is one of the things that having only 1 gulpfile would definitely help with...

[mikemix]

Please don't block me from using the json_manifest_path. I have my own assets to manage.

[teohhanhui]

@mikemix You could always use packages: https://symfony.com/doc/current/reference/configuration/framework.html#packages

[teohhanhui]

If you ask me, all Sylius assets should be under a sylius asset package.

[pamil]

I'd like to help, but my versioning / Gulp / frontend knowledge is not enough here :)

I think we can add sylius asset package without any BC breaks in v1.3.0, wdyt?

[mikemix]

Maybe we could drop yarn too, npm has lock file support too now.

[stale[bot]]

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions.

[mikemix]

Please do not stale :/ you should move to webpack and build proper assets with the content hash.

[stale[bot]]

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions.