CRA overwrites tsconfig, making it difficult to use for maintaining a library

[squidsoup]

I maintain a react component library, written in TypeScript. Our components use sass, and consequently we build the library using babel rather than tsc, and just use tsc for generating type declarations with emitDeclarationOnly: true.

We do want to continue using CRA, however every time we touch react-scripts it adds noEmit: true to our .tsconfig which is incompatible with emitDeclarationOnly. This is very frustrating. Is there a workaround, or has this case been considered by the maintainers?

Thanks

[eddiemonge]

Wouldn't setting the value to false fix that? It looks like it should only replace it when the value is undefined

[squidsoup]

Wouldn't setting the value to false fix that? It looks like it should only replace it when the value is undefined

No unfortunately, the value gets set to true by react-scripts.

[eddiemonge]

thats a bug then and should be an issue, not a discussion. https://github.com/facebook/create-react-app/blob/master/packages/react-scripts/scripts/utils/verifyTypeScriptSetup.js#L103

[squidsoup]

Submitted an issue.

[malcolm-kee]

IMO, CRA is meant for creating SPA, not a library. You may want to explore tsdx which is more customizable and easy to use for creating/maintaining library.