There's a bunch of things you can do to make a choice easier. The most obvious thing you can do is just taking the time you need to make an informed choice. Read the docs, source code, check out known issues, examples, etc. Do you plan to integrate tech X with tech Y? Check if everything you need is supported. Keep notes if it's really overwhelming. You can speed up the process by eliminating choices early if you know your project's hard requirements. If all this doesn't apply to you, e.g. because there are multiple choices that fit your requirements, just pick one and see how it works out for you.
At the end of the day however, you just need to pick something and roll with it. If it turns out not to be the best choice, you'll have at least learned something and the next time you have to choose you'll be better informed.
Don't stress out about it too much. It's a natural part of software development. When you are coding (after selecting all your tools), you are _still making tons of choices_. It's just in a different context; how will you structure your code? What coding paradigm will you apply? What algorithms will you use to solve your problems? You learned to cope with this stress too. It just takes time and experience.
At the end of the day however, you just need to pick something and roll with it. If it turns out not to be the best choice, you'll have at least learned something and the next time you have to choose you'll be better informed.
Don't stress out about it too much. It's a natural part of software development. When you are coding (after selecting all your tools), you are _still making tons of choices_. It's just in a different context; how will you structure your code? What coding paradigm will you apply? What algorithms will you use to solve your problems? You learned to cope with this stress too. It just takes time and experience.