Problem/Motivation

Right now, when "VERSION" is set for the version of a library within a module/theme, the library parser will use the Drupal VERSION constant, which is the current core version. It would be beneficial to have this version key off the module/theme version. This would allow the module/theme libraries to utilize the module/theme version for cache busting when the module is updated.

Proposed resolution

Some possible solutions.

  • The library parser could use the module/theme version instead of the Drupal core version when available.
  • It could also be adjusted to append the module version to the Drupal core version.
  • Another value could be provided to use the module/theme version instead like "MODULE_VERSION"

Comments

dk-massive created an issue. See original summary.

dk-massive’s picture

dk-massive commented
Issue summary: View changes
dk-massive’s picture

dk-massive commented
Issue summary: View changes
dk-massive’s picture

dk-massive commented
Issue summary: View changes
dk-massive’s picture

dk-massive commented
Issue summary: View changes
cilefen’s picture

cilefen commented
Status: Active » Postponed (maintainer needs more info)

This seems similar to #2205027: VERSION in library declarations does not work for contributed/custom modules. Can you verify if this is a duplicate?

quietone’s picture

quietone commented
Status: Postponed (maintainer needs more info) » Closed (duplicate)
Related issues: +#2205027: VERSION in library declarations does not work for contributed/custom modules

I read the other issue and agree it is a duplicate. Since there hasn't been a response, I am going with that and closing this as duplicate.