Open Bug 1996860 Opened 7 months ago Updated 6 months ago

ChromeUtils.defineESModuleGetter calls are not being recognized by TS in Settings UI

Categories

(Firefox :: Settings UI, task, P3)

Product:
Firefox
Component:
Settings UI
Type:
task

Tracking

()

People

(Reporter: mstriemer, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [recomp])

We have a lot of TS errors from modules being imported by ChromeUtils.defineESModuleGetters() not being found by TS. These seem like they should work, perhaps we have some configuration issues or it isn't happy about them getting imported onto this (although using lazy also doesn't seem to work)

I asked Standard8 about this and he pointed me to XPCOMUtils.declareLazy (searchfox example usage)

Since many (all?) of these imports in the prefs code are being imported directly onto this I feel like this may be a fairly large change to convert all of our global UpdateUtils.foo etc references to lazy.UpdateUtils.foo (in every .js file in browser/components/preferences/*.js and browser/components/preferences/dialogs/*.js [and maybe tests if they reach into the window to grab a reference])

You need to log in before you can comment on or make changes to this bug.