ABP 10.7 / LeptonX 5.7 — supported jQuery version set with older bundled plugins #10921

4 Answer(s)

• 

  0

  AI-Bot created 5 hours ago

  Support Team ABP Agent

  • Remove the old Yarn resolution and move to jQuery 4.x (with jquery-migrate 4.x) for an ABP 10.7 / LeptonX 5.7 MVC host.

    • Your current state (jQuery 3.7.1 + jquery-migrate 4.0.2) is internally inconsistent and the runtime error you see is expected: jquery-migrate 4.x requires jQuery 4.x (“JQMIGRATE: jQuery 4.x REQUIRED”).
    • Also, @abp/jquery 10.7.0 declaring ~4.0.0 is ABP’s own signal that the supported baseline for ABP 10.7 MVC bundles is aligned with jQuery 4 (not jQuery 3).

  • Do not try to “force” ABP 10.7’s MVC bundle to stay on jQuery 3.7.1 by pinning/resolutions while keeping ABP 10.7 packages:

    • That creates exactly the kind of incompatible graph you’ve hit (jQuery 3 + migrate 4).
    • If you absolutely must stay on jQuery 3.7.1, the only technically consistent route would be to also keep jquery-migrate 3.x (not 4.x) and ensure all other jQuery plugins are compatible with jQuery 3. However, I could not find a verified ABP 10.7 document/support entry that blesses a “temporary supported configuration” for jQuery 3.x on ABP 10.7 (so this would be an unsupported customization from an ABP supportability standpoint).

  • About the “older bundled plugins” with jQuery <4 ranges (bootstrap-datepicker, timeago, etc.)

    • I do not have a verified ABP 10.7 / LeptonX 5.7 source that states “ABP supports plugin X version Y with jQuery 4” or provides an official replacement matrix for those specific third-party plugins.
    • Therefore, the only definitive ABP-side recommendation I can give (based on verified signals) is: follow ABP’s own dependency direction (jQuery 4 for ABP 10.7 MVC) and then align/upgrade/replace any extra third-party jQuery plugins in your solution that can’t run on jQuery 4.

  • Recommended “supported” configuration for ABP 10.7 / LeptonX 5.7 (MVC host)

    1. Remove any Yarn resolutions/pins that force jQuery 3.7.1.
    2. Restore packages so that @abp/jquery can bring in the intended jQuery ~4.0.0 baseline.
    3. Keep jquery-migrate 4.x together with jQuery 4.x (that’s the compatible pair).
    4. For any additional legacy jQuery plugins you added historically (datepicker/timeago/etc.), upgrade or replace them as needed so they work with jQuery 4.x (this part is application-specific; ABP does not publish a verified per-plugin matrix in the material I could retrieve).

  • Browser flows to exercise (qualification checklist)

    • ABP does not publish (in the sources I could retrieve) an “official MVC/LeptonX jQuery 4 test plan”. Practically, for LeptonX MVC apps, you should at least exercise:
      • Authentication pages (login/logout)
      • Main layout load (side menu/top menu), theme switching (if enabled)
      • Standard CRUD pages generated by ABP (datatables/grids, modals, validation)
      • Any pages using your legacy plugins (datepicker/timeago/etc.), because those are the most likely breakpoints when moving to jQuery 4

  References (validated)

  • https://abp.io/docs/10.7/release-info/migration-guides/abp-10-7
  • https://abp.io/support/questions/5591

  ---

  This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  k.alamri created 5 hours ago

  [AI-Bot] said:

  • Remove the old Yarn resolution and move to jQuery 4.x (with jquery-migrate 4.x) for an ABP 10.7 / LeptonX 5.7 MVC host.

    • Your current state (jQuery 3.7.1 + jquery-migrate 4.0.2) is internally inconsistent and the runtime error you see is expected: jquery-migrate 4.x requires jQuery 4.x (“JQMIGRATE: jQuery 4.x REQUIRED”).
    • Also, @abp/jquery 10.7.0 declaring ~4.0.0 is ABP’s own signal that the supported baseline for ABP 10.7 MVC bundles is aligned with jQuery 4 (not jQuery 3).

  • Do not try to “force” ABP 10.7’s MVC bundle to stay on jQuery 3.7.1 by pinning/resolutions while keeping ABP 10.7 packages:

    • That creates exactly the kind of incompatible graph you’ve hit (jQuery 3 + migrate 4).
    • If you absolutely must stay on jQuery 3.7.1, the only technically consistent route would be to also keep jquery-migrate 3.x (not 4.x) and ensure all other jQuery plugins are compatible with jQuery 3. However, I could not find a verified ABP 10.7 document/support entry that blesses a “temporary supported configuration” for jQuery 3.x on ABP 10.7 (so this would be an unsupported customization from an ABP supportability standpoint).

  • About the “older bundled plugins” with jQuery <4 ranges (bootstrap-datepicker, timeago, etc.)

    • I do not have a verified ABP 10.7 / LeptonX 5.7 source that states “ABP supports plugin X version Y with jQuery 4” or provides an official replacement matrix for those specific third-party plugins.
    • Therefore, the only definitive ABP-side recommendation I can give (based on verified signals) is: follow ABP’s own dependency direction (jQuery 4 for ABP 10.7 MVC) and then align/upgrade/replace any extra third-party jQuery plugins in your solution that can’t run on jQuery 4.

  • Recommended “supported” configuration for ABP 10.7 / LeptonX 5.7 (MVC host)

    1. Remove any Yarn resolutions/pins that force jQuery 3.7.1.
    2. Restore packages so that @abp/jquery can bring in the intended jQuery ~4.0.0 baseline.
    3. Keep jquery-migrate 4.x together with jQuery 4.x (that’s the compatible pair).
    4. For any additional legacy jQuery plugins you added historically (datepicker/timeago/etc.), upgrade or replace them as needed so they work with jQuery 4.x (this part is application-specific; ABP does not publish a verified per-plugin matrix in the material I could retrieve).

  • Browser flows to exercise (qualification checklist)

    • ABP does not publish (in the sources I could retrieve) an “official MVC/LeptonX jQuery 4 test plan”. Practically, for LeptonX MVC apps, you should at least exercise:
      • Authentication pages (login/logout)
      • Main layout load (side menu/top menu), theme switching (if enabled)
      • Standard CRUD pages generated by ABP (datatables/grids, modals, validation)
      • Any pages using your legacy plugins (datepicker/timeago/etc.), because those are the most likely breakpoints when moving to jQuery 4

  References (validated)

  • https://abp.io/docs/10.7/release-info/migration-guides/abp-10-7
  • https://abp.io/support/questions/5591

  ---

  This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

  Thanks—the intended move to jQuery 4 with Migrate 4 is clear. One important clarification: these conflicting plugins are supplied through ABP’s own dependencies, not custom additions. Our MVC host directly references only @volo/account@10.7.0 and @volo/abp.aspnetcore.mvc.ui.theme.leptonx@5.7.0. The ABP shared theme brings in:

  • bootstrap-datepicker@1.10.1: jQuery >=3.4.0 <4.0.0
  • timeago@1.6.7: jQuery >=1.5.0 <4.0
  • jquery-validation-unobtrusive@4.0.0: jQuery ^3.6.0 Could an ABP engineer confirm whether the supported configuration is simply removing our old jQuery 3.7.1 resolution and using jQuery 4/Migrate 4 while retaining these unchanged ABP-managed plugins, despite their declared ranges? If yes, please confirm those range mismatches are expected and supported. If not, please provide the exact supported package versions or official override. We will qualify the confirmed configuration through isolated real-browser checks before closing the finding.

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  AI-Bot created 4 hours ago

  Support Team ABP Agent

  • I can’t confirm (from any verified ABP 10.7 / LeptonX 5.7 source) that ABP officially supports keeping bootstrap-datepicker@1.10.1, timeago@1.6.7, and jquery-validation-unobtrusive@4.0.0 unchanged while moving the MVC bundle baseline to jQuery 4, despite those packages declaring <4 ranges.
    In the verified materials available to me, there is no explicit engineer statement / doc that says “these range mismatches are expected and supported” for ABP 10.7 + LeptonX 5.7.

  • What can be stated definitively and consistently (based on your observed runtime behavior and ABP’s own declared dependency direction):

    1. You must remove the jQuery 3.x resolution (or otherwise stop forcing jQuery 3.x) if the dependency graph brings jquery-migrate@4.x, because migrate 4 requires jQuery 4 (your runtime error is the expected outcome of the mismatch).
    2. If ABP 10.7’s NPM packages you consume truly pull in the listed plugins with <4 ranges while also pulling jQuery 4, then that is an upstream dependency inconsistency that needs an official fix or an official override recommendation from ABP/LeptonX engineering—and I cannot provide that fix/override from verified sources.

  • Because you asked for an “engineer confirmation” / “exact supported package versions or official override”: I don’t have a verified ABP source that provides that confirmation or the override matrix for ABP 10.7 / LeptonX 5.7.0. Therefore I can’t assert supportability of those mismatched ranges.

  • Practical next step (still self-contained, but noting the limitation above):
    If you want a supported answer (not a workaround), this needs to be handled as an ABP support ticket / issue with your yarn.lock (or pnpm-lock.yaml) and the exact dependency tree output showing how those packages are being pulled under @volo/account@10.7.0 + @volo/abp.aspnetcore.mvc.ui.theme.leptonx@5.7.0. ABP can then either:

    • adjust the ABP-managed wrapper packages (@abp/*) to versions whose peer ranges match jQuery 4, or
    • publish an official override guidance for ABP 10.7.

  Sources (validated)

  • https://abp.io/docs/10.7/release-info/migration-guides/abp-10-7
  • https://abp.io/docs/latest/ui-themes/lepton-x/
  • https://abp.io/support/questions/5591

  ---

  This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  k.alamri created 4 hours ago

  [AI-Bot] said:

  • I can’t confirm (from any verified ABP 10.7 / LeptonX 5.7 source) that ABP officially supports keeping bootstrap-datepicker@1.10.1, timeago@1.6.7, and jquery-validation-unobtrusive@4.0.0 unchanged while moving the MVC bundle baseline to jQuery 4, despite those packages declaring <4 ranges.
    In the verified materials available to me, there is no explicit engineer statement / doc that says “these range mismatches are expected and supported” for ABP 10.7 + LeptonX 5.7.

  • What can be stated definitively and consistently (based on your observed runtime behavior and ABP’s own declared dependency direction):

    1. You must remove the jQuery 3.x resolution (or otherwise stop forcing jQuery 3.x) if the dependency graph brings jquery-migrate@4.x, because migrate 4 requires jQuery 4 (your runtime error is the expected outcome of the mismatch).
    2. If ABP 10.7’s NPM packages you consume truly pull in the listed plugins with <4 ranges while also pulling jQuery 4, then that is an upstream dependency inconsistency that needs an official fix or an official override recommendation from ABP/LeptonX engineering—and I cannot provide that fix/override from verified sources.

  • Because you asked for an “engineer confirmation” / “exact supported package versions or official override”: I don’t have a verified ABP source that provides that confirmation or the override matrix for ABP 10.7 / LeptonX 5.7.0. Therefore I can’t assert supportability of those mismatched ranges.

  • Practical next step (still self-contained, but noting the limitation above):
    If you want a supported answer (not a workaround), this needs to be handled as an ABP support ticket / issue with your yarn.lock (or pnpm-lock.yaml) and the exact dependency tree output showing how those packages are being pulled under @volo/account@10.7.0 + @volo/abp.aspnetcore.mvc.ui.theme.leptonx@5.7.0. ABP can then either:

    • adjust the ABP-managed wrapper packages (@abp/*) to versions whose peer ranges match jQuery 4, or
    • publish an official override guidance for ABP 10.7.

  Sources (validated)

  • https://abp.io/docs/10.7/release-info/migration-guides/abp-10-7
  • https://abp.io/docs/latest/ui-themes/lepton-x/
  • https://abp.io/support/questions/5591

  ---

  This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

  Please escalate this existing question to a human ABP/LeptonX engineer. The responses so far acknowledge that the supported configuration remains unconfirmed. We have verified the dependency chain locally: Account 10.7.0 and LeptonX 5.7.0 bring in ABP’s shared theme, which brings in the three listed plugins. These are not custom application additions. We need one actionable engineering answer:

  1. Confirm that jQuery 4 + Migrate 4 with these unchanged ABP-managed plugins is supported despite their declared ranges; or
  2. Provide the exact supported package set, official override, or tracked upstream fix. We use Yarn v1, not pnpm. We can provide sanitized package metadata and relevant yarn.lock excerpts if needed. Please leave this question open pending the engineering response; the compatibility issue is not resolved.

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel