@valerybugakov could you please take a look at this spec PR? We traced all import and require to know which modules are used in a package. WDYT if we follow this https://pnpm.io/blog/2020/10/17/node-modules-configuration-options-with-pnpm#plugnplay-the-strictest-configuration to enable PnP?

@gitstart-sourcegraph, thank you! The spec looks excellent.

Let's first focus on completing the pnpm migration https://github.com/sourcegraph/sourcegraph/pull/46008. The key objective is to make the CI green. Then, we can test this PR properly, relying on CI checks. And after that, we think about enabling PnP in a follow-up PR.

❌ Problem: the label i-acknowledge-this-goes-into-the-release is absent.
👉 What to do: we're in the next Sourcegraph release code freeze period. If you are 100% sure your changes should get released or provide no risk to the release, add the label your PR with i-acknowledge-this-goes-into-the-release.

❌ Problem: the label i-acknowledge-this-goes-into-the-release is absent.
👉 What to do: we're in the next Sourcegraph release code freeze period. If you are 100% sure your changes should get released or provide no risk to the release, add the label your PR with i-acknowledge-this-goes-into-the-release.

Bundle size report 📦

Look at the Statoscope report for a full comparison between the commits 119a400 and f42c059 or learn more.

@valerybugakov We fixed errors on contractors pipeline. Could you please review and give us the errors on other pipelines?

Closing this based on it's interference with the Bezel migration.