Nice! We are still using the react-scripts-typescript fork which made this easy.
I do wish TS would start to support moduleDirs so we can do better shared path resolution!
Fortunately, support for absolute imports using the @ wildcard might be a possibility in CRA 3.0!
While there's nothing wrong with react-scripts-ts, we did switch to react-scripts 2.0 at work for the improved Babel integration, which allows us to use Babel plugins for libraries like styled-components. Fortunately our upgrade path was fairly frictionless.
Also, I forgot to mention it in the post but someone did fork react-scripts-ts in an effort to keep it up to date! github.com/jpavon/react-scripts-ts
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.