That stuff is terrible to use. There is quite a bit of boiler plate involved and there is lots of overhead in general.
Secondly, there are about 10 somewhat popular module formats and they aren't compatible which each other.
I rather do this stuff declaratively. If it's baked into the language, your tools will understand what's going on and there also won't be any compatibility issues. Naturally, it's also way more convenient to use. You just import something. Done.
> doesn't need static typing or other features from TS/Dart
You also don't need a seat belt or airbags. If you don't make any mistakes, you'll be fine.
However, from a pragmatic point of view, these static checks are very handy. If you rewrite some parts of your code, the analyzer will tell you if you screwed something obviously up. It catches all the stupid mistakes, which means you can fully focus on the logical ones.
With JavaScript/Python/etc you have to run the code and actually hit that particular branch to trigger some sort of error/exception which will eventually help you to identify the actual issue.
You should just give it a try. Try any language/IDE combination which offers good tooling. Tooling can remove a lot of friction. There really is a point to all of this.