JS error due to browser cached script after updating to 5.0.1

It seems the most recent release of the library is 3.0.0. I have adjusted the version in the library file to reflect this. I feel this change is in line with the issue and I can certainly confirm the select.oldChosen issue without this patch.

On a second thought, the version number in this case should not be following the chosen library version, but the module version. As this is defining the drupal.chosen assets version and not the library version. The caching issue itself is related to the module's js file (and not the chosen library js). The problem is that the browser returns the cached 4.x version of the module's js.

However, I think the ideal would be to remove the version property (not defining any version). By doing this, Drupal will use an automatically generated query string added to filenames that changes on every update or full cache flush. Like this it won't be needed to always update the version number each time the assets are changed in a new module version. See this issue for entity browser 🐛 Remove VERSION from libraries.yml Fixed for more details.

Patch from MR.

That patch also works on my end and resolves my production issues in the same manner.

I also tested the patch, and it resolves the browser caching issue.

Thanks!

Automatically closed - issue fixed for 2 weeks with no activity.