As all of these provide solutions to create Components, let's categorize your question in two sections, Native and Non-native solutions.
Native: WebComponents which includes Custome Elements, ShadowDOM, HTML Imports, HTML Template, Slots. All info at webcompomponents.org
Non-native: Libs and Frameworks like React, Angular, Vue, Cycle.js etc.
Native solution (by definition) should not require installation; though things are in early phase, the y need polyfills for wide browser support.
Non-native solutions, also don't need anything from user side; though from development side, additional setup is needed the lib/framework at minimum.
Though Non-native tools will let you be more productive and defect free as they handle more and more edge cases by themselves. And native ones give you the freedom, which comes with LARGE SET RESPONSIBILITIES
In the end, you need to install things while developing in any of those because for better readability and manageability, you need those tools.
What differentiates between them is the weight of your code delivered to the user's browser.
P.S__. If you liked the answer, upvote. Having some doubts, comment; lets discuss.
Shameless effort of self publicity: You might wanna have a look at Introduction to WebComponents and ToDo App with WebComponents