To go with the existing "Open npmx.dev in external browser" command it would be nice to see a sibling command that used workbench.action.showIntegratedBrowser to open in the Integrated browser instead of the external browser.
Sometimes I like maximizing VSCode and using complex editor layouts and it would be nice to quickly lookup a npm package in the Integrated Browser instead of the external one.
Oh, bonus points if you make both commands lookup the preferred package manager from the workspace and pass ?pm=<package-manager> so npmx.dev's getting started panel will always suggest the correct install command to copy for that workspace; even if you work in random workspaces that vary between npm, pnpm, bun, or open an old repo that still uses yarn. You probably want a setting to make this optional for the open in external browser command since that affects a device global preference that will follow when opening npmx.dev later and some people won't want their preference affected by random workspaces. But for the Integrated Browser this is probably critical because it may start up with a pristine browser environment and default to npm even if the user has already picked pnpm a thousand times.
To go with the existing "Open npmx.dev in external browser" command it would be nice to see a sibling command that used
workbench.action.showIntegratedBrowserto open in the Integrated browser instead of the external browser.Sometimes I like maximizing VSCode and using complex editor layouts and it would be nice to quickly lookup a npm package in the Integrated Browser instead of the external one.
Oh, bonus points if you make both commands lookup the preferred package manager from the workspace and pass
?pm=<package-manager>so npmx.dev's getting started panel will always suggest the correct install command to copy for that workspace; even if you work in random workspaces that vary between npm, pnpm, bun, or open an old repo that still uses yarn. You probably want a setting to make this optional for the open in external browser command since that affects a device global preference that will follow when opening npmx.dev later and some people won't want their preference affected by random workspaces. But for the Integrated Browser this is probably critical because it may start up with a pristine browser environment and default tonpmeven if the user has already picked pnpm a thousand times.