Skip to content

Fix duplicate module init when using Vite in EE and JH editions

Stanislav Lashmanov requested to merge slashmanov/fix-vite-duplicate-module-init-with-EE-and-JH into master

What does this MR do and why?

This fixes a bug in Vite frontend integration when CE entrypoints were still loading while the EE and JH entrypoints for the same path were present.

Example paths:

  1. app/assets/javascripts/projects/issues/show/index.js
  2. ee/app/assets/javascripts/projects/issues/show/index.js

Only the second one should be loaded.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

How to set up and validate locally

  1. Enable EE (Enterprise Edition) features, requires license
  2. Open issue page
  3. Ensure CreateMergeRequestDropdown is initialized only once (put a debugger statement in the constructor)

Merge request reports