VERSION in library declarations does not work for contributed/custom modules

Created on 25 February 2014, over 10 years ago
Updated 7 March 2024, 4 months ago

Problem

  1. Only core modules are able to specify version: VERSION in their declared libraries, because the version of a core module is the version of Drupal core.
  2. In case a module or theme is updated, then the version query string that is appended to the library asset files on output will not reflect the new version.
  3. The version of a non-core module has to be retrieved from the extension system.

This may or may not be resolved by #2203411: Convert drupal_get_library() into a service β†’ , so tracking as an independent issue to be sure that we will resolve it.

πŸ“Œ Task
Status

Needs work

Version

11.0 πŸ”₯

Component
Asset libraryΒ  β†’

Last updated about 13 hours ago

No maintainer
Created by

πŸ‡©πŸ‡ͺGermany sun Karlsruhe

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡©πŸ‡ͺGermany diqidoq Berlin | Hamburg | New York | London | Paris

    Haven't read yet over all comments but found parallel thougths of what brought me here in the intial issue summary point 1.) and in comment #3 or nod_ while I was fixing library.yml version issues in contrib modules.

    What if we simply use the module version created by packaging script as /?version-path-suffix for library files and deprecate the tag for library files completely? Is that possible? (Drawback: no manual override possible then. But for what should that be needed?) This could be a solution for both, contrib and core (at least in my head)

Production build 0.69.0 2024