@tarasm Ember itself is focused on whole-page apps with multiple routes. Solving that results in a very different solution than what is needed for one-part-of-page-interactivity. That said, if you want components or only parts of Ember, you can customize the build. I’ve got an example of that here:
Ember is built from several micro-lib dependencies and several internal packages. Customizing the build is all about picking and choosing which packages to put together.
The result probably isn’t as lightweight as you would hope (though the sizes in that post must be out of date). Maybe you can get a better size by further tweaking what packages you require.