deno bundle silently drops npm dependencies

[mcodik]

I understand that npm module specifiers arent supported yet in deno bundle in 1.28.0, and I see its TODO in #15960.

However, if you try to use deno bundle on a script with an npm module import, it emits a bundle with the dependency missing, so if you try to execute the bundle you get a runtime error.

Can deno bundle can fail with an error code when it encounters npm module specifiers until support is added?

example code, which works fine in deno run:

import _ from "npm:lodash@4.17.21";

const salutations = ["Hello", "Hi", "Howdy", "Hola", "Salut"];
const salutation = _.sample(salutations);
console.log(salutation);

deno bundle output:

// deno-fmt-ignore-file
// deno-lint-ignore-file
// This code was bundled using `deno bundle` and it's not recommended to edit it manually

const salutations = [
    "Hello",
    "Hi",
    "Howdy",
    "Hola",
    "Salut"
];
const salutation = __default.sample(salutations);
console.log(salutation);

which fails at runtime because __default is undefined