Tworzenie aplikacji internetowych po stronie frontendu (tego przeglądarkowego) jest coraz bardziej złożone. Od dłuższego czasu coraz więcej projektów korzysta z TypeScript jako bazowej składni JS, co wiąże się też z tym że wymaga to skonfigurowania odpowiedniego środowiska developerskiego. Dalej
W procesie tworzenia stron internetowych jest wiele różnych etapów. Zaczynając od utworzenia środowiska, po wybranie odpowiednich narzędzi, a następnie zaprojektowanie i zakodowanie strony według wymagań.
Dalej
In my work I often find myself in situation where designers are using colors that are not defined in the style guidelines, but are somewhat similar. This is a difficult situation for every frontend developer that would like to use only colors predefined in guidelines for consistency.
Dalej
When I started learning Typescript with React I was able to stick with the convention of defining components with a const keyword. After some I switched teams and we decided to use function declarations as a convention for defining React components.
When developing apps using modern syntax following ES6+ standards you can get to the point that your files and directories structure is deeply nested. This makes importing code a little bit complicated.
Dalej
When writing React apps or modern JavaScript in general, we often create files with a set of reusable functions or classes. People tend to use default exports in such cases and I'm going to explain, why it's not the best idea to use them.
Dalej
We all know what React is today. For those who don't know it yet: it's a view rendering library that helps developers to build user interfaces rapidly.
Dalej
Recently I've been in the situation where I needed to resolve multiple async functions in paralel. The tricky part was that these functions were written using async/await approach and I was going to use Promise.all() function to resolve all of the async requests at the same time, when all of them are resolved.
