4 ms·
I do not have any particular request for the team. At office we love react and the journey of porting legacy to it has been enjoyable. One thing that is someho
by mcs_ 8y ago
I do not have any particular request for the team. At office we love react and the journey of porting legacy to it has been enjoyable.
One thing that is somehow frustrating with multiple repositories are those shared components.
I know this is not directly an issue with react itself but after create-react-app one, two, three. ... times the amount of duplicated code/components become a huge debt.
I'm not sure I need something new/different from react@next but guidelines for creating libraries and produce high quality components (type definition done right for example) is something that I'd like to have.