How future-proof is this module?

Created on 12 March 2024, 8 months ago
Updated 17 March 2024, 8 months ago

First off, this module works perfectly and is great! However, before using it, I'd like to have a better understanding of the future implications. My main concern is: What are some possible future scenarios that might give me a headache if I'm using this module?

For example, is there a chance that Drupal core might someday require some new JS function that is not in the files being used here? (Or something like that?)

πŸ’¬ Support request
Status

Active

Version

1.0

Component

Miscellaneous

Created by

πŸ‡ΊπŸ‡ΈUnited States brockfanning

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

Comments & Activities

  • Issue created by @brockfanning
  • πŸ‡ΊπŸ‡ΈUnited States brockfanning
  • πŸ‡¨πŸ‡­Switzerland florianmuellerch Aarau, Switzerland

    Hi @brockfanning, thank you for your interesting question!

    I personally assume that Drupal Core aims to remove jQuery alltogether, leading to both core/jquery and core/jquery.once libraries being dropped out. I plan to keep this module as compatible as possible for as long as possible because I simply like the way jQuery and jQuery.once work.

    The only way this module would not be future-proof is if core decided that under core/jquery they release a piece of software that is different from default jQuery versions, and would be missing as we simply override it. But this would in fact break a lot of existing installations even more, so I don't see any evidence of this.

    As a last resort, you could always take the code of this module (which is really fairly simple) and put it in your own module and adapt some changes, if you need something urgently. However I would assume that others might encounter the same issues, raising the need for an issue here in the issue queue to tackle the problem for everybody.

    Have a great sunday and a nice week,
    Florian

Production build 0.71.5 2024