feat: bring back browser extension

[svrnm]

Which problem is this PR solving?

This PR brings back the browser extension by fixing the build errors & updating dependencies and some, see #1101, #1110

Short description of the changes

• Move extension back to packages
• Update dependencies until npm run compile works again
• Update some of the dependencies and words (e.g. move from "Collector Trace" to "OTLP HTTP" exporter, etc.)
• Add some clean ups
• Add myself as component owner
• Add a server folder that contains instructions on how to run a collector behind a nginx for proper CORS headers.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.13%. Comparing base (dfb2dff) to head (6118091).
Report is 162 commits behind head on main.

❗ Current head 6118091 differs from pull request most recent head 8006737

Please upload reports for the commit 8006737 to get more accurate results.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1152      +/-   ##
==========================================
+ Coverage   90.97%   96.13%   +5.15%     
==========================================
  Files         146       14     -132     
  Lines        7492      906    -6586     
  Branches     1502      197    -1305     
==========================================
- Hits         6816      871    -5945     
+ Misses        676       35     -641     

see 134 files with indirect coverage changes

[svrnm]

not sure how to fix the issues with node 8 & node 10. Best option would be to exclude them, since the final runtime is the browser and the testing doesn't need to run on all node versions.

[dyladan]

Failure appears to be a dependency conflict due to webpack versioning differences with other packages in the repo

[svrnm]

Failure appears to be a dependency conflict due to webpack versioning differences with other packages in the repo

looks like I still have to learn about lerna and stuff... let me see if I can get this working somehow, because updating to a more recent version of webpack did the trick to get it compiled again, and downgrading sends me into a rabbit hole of dependency issues.

[blumamir]

@MSNev aligned the webpack versions in #1264
Maybe rebasing main will fix the CI?

[blumamir]

Also related - renovate's #1258 and #1123

Might be a good chance to upgrade these as well while we are at it, if you can

[blumamir]

Why upgrade the "@opentelemetry/api" minimum supported minor versions?

If the user is using an older version of the API, will it fail to work?

[svrnm]

Not sure why I changed it, it should work with 1.0 as well

[github-actions]

This PR is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.

[SimenB]

Still interesting in seeing this land 😀 anything I can do to help it along? #1486? it was closed without attention…

[svrnm]

Still interesting in seeing this land 😀 anything I can do to help it along? #1486? it was closed without attention…

Hey @SimenB, thanks for your interest in this! I was ooo the past few days and couldn't follow up. I think there are 2 options how to fix this, bumping webpack dependencies to 5. like in #1486 is the "better" solution, the other option is making the extension work differently (replace webpack with something else)

[github-actions]

This PR is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.

[SimenB]

Seems that other PR just needed webpack in order to work work with karma. Seeing as karma is deprecated, it might be better to just migrate to another test runner that doesn't webpack to begin with.

[svrnm]

Seems that other PR just needed webpack in order to work work with karma. Seeing as karma is deprecated, it might be better to just migrate to another test runner that doesn't webpack to begin with.

wow, highly appreciated @SimenB !

[JamieDanielson]

Sorry on the delay on this. It's been several months since this was last updated, but @svrnm are you still interested in maintaining this? It seems like the blocker right now is to update web tests to use web-test-runner instead of karma. @SimenB already got the updated test runner in #1816 and there is an open PR with an error #2005.

We'll try to take a look at #2005 either way and as a follow-up will want to get the rest of the web components updated to use web-test-runner instead of karma. But still it will be useful to know if you are still interested in maintaining this or if it's no longer a need right now.

[svrnm]

Sorry on the delay on this. It's been several months since this was last updated, but @svrnm are you still interested in maintaining this? It seems like the blocker right now is to update web tests to use web-test-runner instead of karma. @SimenB already got the updated test runner in #1816 and there is an open PR with an error #2005.

We'll try to take a look at #2005 either way and as a follow-up will want to get the rest of the web components updated to use web-test-runner instead of karma. But still it will be useful to know if you are still interested in maintaining this or if it's no longer a need right now.

I am happy to maintain this, if the tests are unblocked now, or if this requires me to rewrite the tests with web-test-runner instead of karma I can look into that.

[JamieDanielson]

I am happy to maintain this, if the tests are unblocked now, or if this requires me to rewrite the tests with web-test-runner instead of karma I can look into that.

Ok thanks for the confirmation! On #2005 we seem to have found the cause of the errors on updating to use the new test runner, so we should be able to keep moving forward on those. If that's an area you're familiar with it's always useful to have your input or feedback on those changes 😃

We'll probably want to add a commit or otherwise kick the CI to see the latest on lint and test results.

[pichlermarc]

We've hit some roadblocks with updating to @web/test-runner (missing named exports from the shimmer package, which don't play well with rollup), so I tried again to update webpack to v5 as we've done that in the core repo previously. Workflows are passing, so this might unblock this PR. See #2269

[pichlermarc]

I just merged #2269. The outdated webpack version should now not be a problem anymore 🙂

[svrnm]

That's great news, @pichlermarc! I'll look into it eventually to fix the extension

[svrnm]

FYI, since the code hasn't been touched for that long it will take me some time to get everything back in place

[svrnm]

Note, that after discussing this with @JamieDanielson and @pichlermarc I will not bring back this browser extension to reduce the maintenance burden for the maintainers and myself. Instead I work towards listing existing extensions (like https://github.com/tbrockman/opentelemetry-browser-extension) on the Registry and then link out to the registry via the README of the archived extension.