Fix errors when importing Glean.js in Typescript environments

[brizental]

Currently when attempting to import the @mozilla/glean package in the Bergamot extension, we get the following error:

Cannot find module '@mozilla/glean/webext' or its corresponding type declarations.

I am mostly sure that the problem is with our types definitions. If you look at this thread , you'll notice that it is not ironed out exactly how exports and type declarations play together.

I have used the typesVersions workaround since the change to use exports, because I am basing myself off of how jose does thigs.

I seem to be using it incorrectly. In this branch I made some experiements. You'll see that I included conditional imports for different environment, after noticing that bergamot is expecting commonjs modules. That was not the issue, but since I've already done the work I decided to keep it (we had a bug for it anyways).

Playing around with the typesVersions field was more promising. The way that is is right now I finally don't get an error when importing Glean in in the Bergamot extension 🎉

I also don't get an error when running yarn run build:production. Yay!

Sadly the minute I use the imported Glean object, either through Glean.initialize or even console.log(Glean) I get back to the same Cannot find module....

Also this only solves the /webext import, when attempting to do something like /webext/private/ping for example, we get back to not being able to import.

[brizental]

Thought: Seems like the import cares about the path for the types definitions (notice that in the vscode screenshot I provided the module path points to its type defiitions). Maybe, it error only when I actually call Glean, but the actual code is only imported upon first call, up until then it only cares about types definitions.

I have no basis for this claim, just assumptions based on these experiences. Could be due to the usage of yarn maybe? Remember the import errors do not happen in our own sample web extension.

[Dexterp37]

r+wc