There are 35 extensions having a ResourceModules with a dependency upon a module that starts with ext.visualEditor:
AtMentions BlueSpiceProDistributionConnector BlueSpiceVisualEditorConnector Chart Checklists Cite Citoid CodeMirror CognitiveProcessDesigner CollabPads ContainerFilter ContentDroplets ContentTranslation DateTimeTools Disambiguator DiscussionTools EnhancedUpload Flow GrowthExperiments Kartographer LanguageTool Math PDFCreator ProofreadPage Sanctions Score SimpleTasks SoftRedirector SyntaxHighlight_GeSHi TEI Translate VECancelButton VEForAll VisualEditorPlus wikihiero
They would need VisualEditor to be explicitly defined as a dependency in order to fullfil MediaWiki core test ResourcesTest::testValidDependencies.
I went with a small python script:
parse_extensions
#!/usr/bin/python from glob import glob import json import os.path import yaml with open( os.path.expanduser('~/projects/integration/config/zuul/dependencies.yaml') ) as f: ci_deps = yaml.safe_load(f) for ext in sorted(glob('*/extension.json')): name = os.path.dirname(ext) if name == 'VisualEditor': continue if 'VisualEditor' in ci_deps.get(name, []): continue with open(ext) as f: registry = json.load(f) for module_name, module in registry.get('ResourceModules', {}).items(): if any( dep for dep in module.get("dependencies", []) if dep.startswith('ext.visualEditor.') ): print('|', name) break
Which gives:
| BlueSpiceProDistributionConnector |
| Chart |
| CognitiveProcessDesigner |
| PDFCreator |
| Sanctions |
| SimpleTasks |
All of them currently get VisualEditor as a transitive dependency with the exception of PDFCreator.