As others have already said, the prohibition of using the code in commercial applications would make the license not open source/free software (as defined by the Free Software Foundation and Open Source Initiative.)
These are some of the most commonly used licenses:
MIT - a very permissive license. Roughly says "do anything with this as long as you give attribution"
BSD - similar to MIT (note that there are multiple versions of the BSD license)
ASL2 - another permissive license. Major difference is that it also includes a patent grant clause. (Mini rant: I often hear that GPL3’s patent clause is the reason big companies don’t like it. Yet, ASL2 has the very same clause and it’s Google’s favored license.)
GPL - the most popular copyleft license (family). Requires derived works to be licensed under the same terms.
LGPL - a variant of the GPL that permits dynamic linking to differently licensed works. Mainly useful for libraries.
AGPL - a variant of GPL that specifies that making the software available over a network counts as distribution. (Works around the SaaS loophole. Mainly used for server applications.)
Mozilla - a hybrid permissive/copyleft license. I don’t fully understand how this one works.
If you want to use a true FLOSS license and your goal is to discourage people from selling it, I’d say the GPL is your best bet. Legit vendors who don’t want to give out their source code won’t touch GPL code. The non-legit ones won’t care no matter what license you choose. Also, iOS App Store terms are not compatible with the GPL so they can’t release their stuff there, but you can as long as you hold full copyright to your application.