In general, there are two major reasons to use DI. The first is testability, as testing frameworks for TS/JS can override imports, that lessens the use case significantly. The other is to easily target multiple plugins/modules that can be changed out. If you aren't actively targeting multiple versions or plugin models, that lessens the second reason.
For most developers, most of the time, hard coding to an instance/module and using the testing frameworks to override those imports is less cumbersome than the overhead to reason with DI abstractions when spelunking through code in the future.