For instance, bundling typescript. I like typescript and hate setting up the build toolchain so this sounds like a good idea. But not every typescript upgrade is backwards compatible (even if unintentional when not), and I'd hate to be stuck not upgrading V8 because it's bundled with typescript.
Or the import system. Importing from HTTP is useful, it ensures things "just work". I like it, on first sight. But is it manageable? Let's say I isolate all my external dependencies into files that just re-export them, or whatever the standard is nowadays. Is the tooling there for when I need to upgrade? How do I deal with sub-dependencies using different versions of things? How do I keep versions compatible? Will something break if I depend on Xv1.1 and Yv1.2 and X uses Yv1.3? Can I force X to use Yv1.2? I can see a world where these things are solved, but it's a vague image.
Or the permissions. Why does my text processing app need to access the web? Again, seems like a good idea. But now the behavior of your standard library is tied to cli options. Phone apps make this work, but they request permissions, you don't explicitly say, "Open Maps with internet access". Ideally I'd like my code not to behave too differently just because it's in a different environment. I want to believe, I see a world where this all comes together smoothly, but it's tough to trust right now.