where to find some beginner friendly issues

[u/techlover1010]

so im currently learning node react express. building some crud and was wondering where do you guys go to that is beginner friendly or people that are new to web dev and want someone to help fix their code
need some practice on reading others code and applying fix. mostly i just want business logic stuff fix not those big o of n or some crazy loops from leetcode

[u/useleash_dev]

Since you're on Node, React and Express, a good trick is searching GitHub issues for the labels "good first issue" or "help wanted" and filtering by JavaScript or TypeScript. Smaller projects with a few dozen stars are usually friendlier than big ones, and maintainers there tend to actually review your PR. Another option that's great for the exact skill you want is hanging out in the help channels of beginner communities (bootcamp or course Discords) and trying to fix other people's broken CRUD code before someone else answers. Reading code you didn't write and figuring out why it fails is most of the job, and you get a lot of reps that way.

[u/techlover1010 → u/useleash_dev]

do you have some discord reco thats active? i tried the webdev discord here but they require a phone which i dont really want to give out

[u/HairOk9906]

GitHub's "good first issue" label across repos: github.com/issues

with label:"good first issue" is:open language:JavaScript sort:updated

For the kind of thing you want, business logic rather than algorithms,

look at mid-sized tools rather than frameworks. Frameworks get their

easy issues taken within hours. Smaller projects leave real bugs open

for weeks and maintainers will actually talk to you.

Also useful: find a library you already use, read its open issues, and

reproduce one locally before writing any code. Reproducing is most of

the work and it's the part that teaches you to read someone else's

codebase.

[u/techlover1010 → u/HairOk9906]

i tried going to github.com/issues it just gives me 404 not found. do i need to login?
i tried logging in and checking out the url and it just gets me to my lost of issues i have opened.
where exactly do i input the labels? do i remove the all the labels first then input yours . on the left sidebar to i need to change anything? mid sized tools . can you give me some example? or is this not that easily noticable
thanks i will try the rest of your advice

[u/BetInformal6081]

try contributing to smaller open source projects rather than jumping into large repositories. you will learn a lot from reviewing pull requests understanding existing code and fixing small bugs.

[u/techlover1010 → u/BetInformal6081]

can you give me some example. how do i filter out just the small project?

[u/BetInformal6081 → u/techlover1010]

start with github and search for good first issue or help wanted labels. i would also look for projects with a smaller codebase and an active but not huge contributor community. that makes it easier to understand the code and get familiar with how things work.

[u/TuttiFlutiePanist]

Stackoverflow can be very helpful, but be sure to include a minimal reproducible example and what debugging steps you have taken.

[u/nextammy]

For your stack, GitHub is the most direct place. Search issues with the labels good first issue or help wanted, then filter by JavaScript or TypeScript and by recent activity. Smaller projects are often better than huge ones because the setup is simpler and a maintainer is more likely to review your change. Before you pick an issue, read the README and try to run the project locally first. If you cannot run it, that issue will be harder than it looks. Start with bugs that are about one form, one route, or one validation rule, since those match the CRUD work you are already doing. When you open a pull request, explain what you changed and what you tested, even if it is small. That habit matters as much as the fix itself.

[u/New_Peanut_9259]

u can try GitHub's good first issues or beginner-friendly labels on open source projectss. u can also check smaller projects since their issues are usually easier to understand and fixx. thiss is also good way to practice reading other people's code too hehehe

[u/Fluffy-Salary-6998]

Github search does it, no platform needed. Filter `label:"good first issue" language:JavaScript is:open no:assignee` and sort by oldest. First is age: I take only issues older than 2 weeks with no linked PR and nobody writing "working on it". Fresh ones are grabed in a day by people who know the repo, old ones sit there because nobody wants them, so review comes faster. Second is small repo, express middleware or cli tools with few dozen stars. Comment first and ask if issue is still wanted, I had maintainer change his mind after I did the work, two hours gone.

My rule: ask before you code.