.npmrc.npmrc that has rules like this:import { foo } from '@custom/foo'import { foo } from '@custom/foo' to be loaded from that specified registry instead of the default NPM registry, using the configured authTokenauthToken. It leaves all other NPM packages to continue being retrieved via the default registry.NPM_CONFIG_REGISTRYNPM_CONFIG_REGISTRY@custom@custom scope. So when it comes to something like lodashlodash, it fails trying to fetch lodashlodash from npm.example.comnpm.example.com.export DENO_AUTH_TOKENS="DEADBEEF@npm.example.com"export DENO_AUTH_TOKENS="DEADBEEF@npm.example.com"https:https:. I suppose it's treating it as if it were retrieving a deno package from the denoland package registry.Join the Discord to continue the conversation