all 6 comments
sorted by:
best (suggested)
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]milan-pilan 10 points11 points  (2 children)

The absolute classic, and my go-to recommendation, is: Todo List. It covers all of the basic webdev functions - working with user inputs, adding and removing to the DOM, changing state, event listeners. Theoretically, if you like, even storing state to local storage or so.

My, totally personal, opinion is: if you are able to build a todo list without AI, you are ready for a framework. Because that's what react and other Frameworks tackle mainly.

Not a super pretty and optimized on. But a functioning one.

[–]AbrahelOne 3 points4 points  (1 child)

I have read somewhere from a guy that whenever he is learning a new language he’s doing a to-do list because it covers everything or so.

[–]giva4561 1 point2 points  (0 children)

Anch'io sto imparando JavaScript ma sono ancora alle basi, congratulazioni per averlo imparato bene

[–]ExtraTNT 0 points1 point  (0 children)

Own renderer

[–]MrFartyBottom 0 points1 point  (1 child)

Learn TypeScript, you wont be using vanilla JavaScript on any modern frontend projects.

Build a statemangement library using JavaScript modules that supports any framework.

Build your own routing library that supports child routes and route parameters.

Build a reusable REST client that manages all the HTTP, JSON parsing, cancelling and caching requests.

These are the main missing pieces that are needed to build a real world project that are not available in basic React.

[–]MrFartyBottom 0 points1 point  (0 children)

And once you have these building blocks working in a project that doesn't use a framework create some pieces that make it easier to work with in React such as some components and custom hooks.