There are dozens of uses of ChromeUtils.import with null as the second parameter. This is deprecated, so we should move away from it.

https://searchfox.org/mozilla-central/search?q=ChromeUtils.import%5C(%22%5B%5E%22%5D%2B%22%2C+null%5C)%3B&case=false&regexp=true&path=extensions%2F

28 occurrences use Management, which can simply be replaced with ExtensionParent.apiManager. There are probably also a few other simple fixes, and some possibly more difficult cases.

Simplify some instances where modules were lazy loaded.

Hi Mathew, are you still working on this? The other patch that I mentioned in Phabricator landed a while ago.

I'm still planning to work on it. It might take me some time because I need to setup my environment and rebase.

(In reply to Mathew Hodson from comment #3)

I'm still planning to work on it. It might take me some time because I need to setup my environment and rebase.

If you're looking for a written guide, see the section and/or linked documentation at https://wiki.mozilla.org/WebExtensions/Contribution_Onramp#Setting_Up_Developer_Environment

Just to note, I'm going to be filing bugs to fix the other import rule failures referenced in the .eslintrc.js file, so you may come across bitrot there.

Also, I've just been told that it would be useful to have this within the next few weeks, as we are hoping to move forward with work that this enables.

https://hg.mozilla.org/mozilla-central/rev/d5698a41fbcc

Thank you for working on, that's a really nice big bit of clean-up to have done.