Personally, I make sure that on a resume I clearly distinguish between the things that I have mastered and the things that I am familiar with.
The things that I have mastered and are most relevant to the position, I make sure are at the top of my resume and stand out somehow (bold, bigger font, etc).
Things that I am only familiar with, I first decide if they are relevant to the position. If they are completely irrelevant, I wouldn't even include them, as they are just noise at that point. I hate when I have to interview someone and I look at their resume and it's just a comma delimited list of 30 different irrelevant technologies. It also makes me question their implied experience level in all of these different things.
If I have done some research into a relevant technology, I would make it clear that I am familiar with it, but by no means an expert. The language you use here can be important. For example, if you said you are experienced with Angular.js, I would take that to mean that you are pretty competent and knowledgeable about it. If you say you have experience with it or are familiar with it, then I would think you are maybe not an expert, but could get up and going with it fairly quickly.
If you are not confident enough to have either of these assumptions made, I would not list it at all, but maybe bring up the fact that you have been doing some personal research into it during the interview itself