4 ms·
Nowadays the only choice you’re really making is which styling library to use and which state management. Everything else is a given. Anyways, if you know enou
by dntrkv 5y ago
Nowadays the only choice you’re really making is which styling library to use and which state management. Everything else is a given.
Anyways, if you know enough about FE to have an opinion on the tooling, great, choose what you want. If you don’t wanna choose, use Next.js or CRA with React/Styled-Components and then add React Router if you need routing and add state management if you need it.
These aren’t difficult choices to make. I have a feeling that the problem is that people are trying to make decisions they don’t need to be making up front.
Evaluate the choices when you reach a situation that requires it.
- neves 5y ago> Everything else is a given. Would you please send a link that summarizes this "everything else"? Every time I take a look at JS ecosystem I get lost.
- dntrkv 5y agoReact, Webpack, Eslint, Jest, React Testing Library That’s the standard setup nowadays and it’s what most people should go with. If you want type checking, add TS to the mix. But seriously, just use Next.js you can build tiny static sites with it and you can build complex SPAs. It’s very lightweight and basically just strings together all these tools while adding some convention that you can follow if you wish.