My experience is that the more things needed to be aliased the harder it get's to scale. When it comes to styled-components it's easy to alias in the webpack configuration because they offer packages for both sides. For the web side they have their normal package styles-components and for react-native they have styled-components/native package.
I have not personally used a11y in this case, and I'm not sure how you are using it. but I'm going to guess you will need to think about how it's used on both sides, web+native
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thank you for the response!
My experience is that the more things needed to be aliased the harder it get's to scale. When it comes to styled-components it's easy to alias in the webpack configuration because they offer packages for both sides. For the web side they have their normal package
styles-componentsand for react-native they havestyled-components/nativepackage.I have not personally used a11y in this case, and I'm not sure how you are using it. but I'm going to guess you will need to think about how it's used on both sides, web+native