gnome-shell/subprojects/extensions-app/js/org.gnome.Extensions.in

import {programInvocationName, programArgs} from 'system';

imports.package.init({
    name: '@PACKAGE_NAME@',
    version: '@PACKAGE_VERSION@',
    prefix: '@prefix@',
    libdir: '@libdir@',
});
const {main} = await import(`${imports.package.moduledir}/main.js`);
await main([programInvocationName, ...programArgs]);
extensions-app: Port to ESM The extensions app is another part of the code base that is largely separate from the main code base, and can therefore be ported to ESM before the big switch. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2786> 2023-05-25 15:23:24 -04:00			`import {programInvocationName, programArgs} from 'system';`

			`imports.package.init({`
extensionPrefs: Use imports.package.start() We want to make the extensions app code more self-contained to make it easier to build separately, and ultimately make it available on flathub. One complication we are facing is that it is currently all over the source tree: - js/extensionPrefs for the main code - src for the launcher process - data for .desktop file and icons Switching from a C launcher to the imports.package module allows us to consolidate the first two, and will also take care of the annoying setup bits (defining JS search path, extending GI lookup, loading resources). https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1081 2020-03-05 11:44:27 -05:00			`name: '@PACKAGE_NAME@',`
			`version: '@PACKAGE_VERSION@',`
			`prefix: '@prefix@',`
			`libdir: '@libdir@',`
			`});`
extensions-app: Port to ESM The extensions app is another part of the code base that is largely separate from the main code base, and can therefore be ported to ESM before the big switch. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2786> 2023-05-25 15:23:24 -04:00			const {main} = await import(`${imports.package.moduledir}/main.js`);
			`await main([programInvocationName, ...programArgs]);`