This call to "require" will not be bundled because the argument is not a string literal (surround with a try/catch to silence this warning)

[Valexr]

Can't bundling mongoose module

[ggoodman]

Looks like a dupe of #1127.

EDIT: Looked more into this, and I don't believe it is a dupe after all. This sort of dynamic dependency resolution is really problematic for bundlers. Figuring how those dependencies during bundling is pretty tricky. It would require the bundler to be able to statically evaluate the value of global.MONGOOSE_DRIVER_PATH (in the first) and of driver (in the last 2) warnings. In many cases this will be impossible / impractical. Different bundlers have different levels of sophistication with their heuristics to solve this sort of thing.

[Valexr]

Yep... seems like this... internal require(foo + 'string') not string literal in imported module don't bundling...

[evanw]

Yes, it's not possible to bundle things like this. The warnings are correct. They are warnings instead of errors because your bundle could hypothetically still work if these code paths are not relied upon. But if you need this to work then you're out of luck. You'll either have to run the code unbundled or use another tool instead of esbuild.

[evanw]

Closing this because this is by design.

[Valexr]

Ok. Tx for res @evanw 🤓

[ndr47]

Does somebody know any workaround to bundle mongoose module with this?