React
almost exclusively with hooks, mostly web applications (not simple sites) with a lot of state and API calls🚧 The extended CV is currently very much WIP. Should be ready in a few days. 🚧
almost exclusively with hooks, mostly web applications (not simple sites) with a lot of state and API calls
using proper TS (not many anys to be found) and swapping to JS only in rare occasions (eg. some small utility CLI tools)
with Apollo or URQL client, end-to-end type safety with TS, generated types and hooks based on frontend documents
mostly with axios, some experience with fetch, not much with other libs
default, go-to solution for state management, suitable for small to medium apps
used for few pieces of more complicated state
used in multiple apps for managing the state of larger forms
would like to try it out and possibly use it as a default state management solution
would really like to get more into schema validation – especially when working with REST APIs, but also for data stored in persistence
used a lot in the past, but now I try to get more into build time solutions
built an internal component library on top of Chakra, used it in multiple applications
used in my personal website, really liked it as a modern, viable CSS-in-JS solution
not really styling, but I have tested it in one project and it seems like a good base for building accessible components
would really like to do more with it, seems fun
used daily, know the basics (including rebase, cherry-pick, etc.), but only in a small team where conflicts were mostly avoidable (mostly on Bitbucket)
try to write semantic HTML and use the right tags for the right job whenever possible
can write my own styles, confident when using both flexbox and grid layouts, mostly using CSS-in-JS or CSS modules
love the tool, used in multiple projects for UI lib development and documentation, would like to try visual testing as well
not used to write unit tests as most of the business logic in apps I worked on was on the BE side, I understand the importance of it though
E2E tests make the most sense to me – I have used Cypress in few projects to ensure core functionality works as expected
connected to multiple projects both in React and React Native to keep track of user errors
the editor of choice, using shortcuts, command palette, various extensions and even custom snippets!
using these in every project, although I would prefer prettier to be less opinionated sometimes
used and set up few of these, most recently using TurboRepo, but would like to try Nx as well
never had a need to use it, but I understand the benefits and would like to get into it one day
created multiple applications for both Android and iOS, all using Expo and without a need to write custom native modules
a go-to default for any new React app, built few applications both with pages and app directory router