Bug from polyfill being a nested dependency?

[tbjgolden]

When running extension dev for chromium

►►► Using own Chromium browser binary /usr/bin/chromium. 
✖︎✖︎✖︎ ExtName compiled with errors in 579 ms.
ERROR in ./popup.ts 37:27-34
  × Module not found: Can't resolve '~/extname/node_modules/extension-develop/node_modules/webextension-polyfill/dist/browser-polyfill.js' in '~/extname'
   ╭─[1:0]
 1 │ import { readS, writeS } from "settings";
   · ▲
 2 │ import img from "./icons/128.png";
 3 │ function insertVDOM(el, vdom) {
   ╰────


ERROR in ./settings.ts 33:10-17
  × Module not found: Can't resolve '~/extname/node_modules/extension-develop/node_modules/webextension-polyfill/dist/browser-polyfill.js' in '~/extname'
   ╭─[1:0]
 1 │ export const DEFAULT_SETTINGS = {
   · ▲
 2 │     dialect: "auto",
 3 │     mode: "glow",
   ╰────

my current hacky solution is to just do this, but I wonder if this could be fixed in the packages itself

~/extname on  main [!] via  v22.16.0 took 8s 
❯ cd node_modules/extension-develop

~/extname/node_modules/extension-develop on  main [!] is  v2.0.0-rc.38 via  v22.16.0 
❯ npm i && npm add webextension-polyfill

note: npm (at least recent versions) don't install dependencies deeply