Skip to content

Monorepo and CRA 2 #29

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
deftomat opened this issue Oct 10, 2018 · 2 comments
Closed

Monorepo and CRA 2 #29

deftomat opened this issue Oct 10, 2018 · 2 comments

Comments

@deftomat
Copy link

deftomat commented Oct 10, 2018

I'm having issue with monorepo with a multiple TypeScript packages.

Previously, I was able to import any TypeScript file from another package and compilation will handle it. However, after upgrading from 2.0.0-next.3e165448 to 2.0.4 typescript files from another packages or even from another directory than src are not compiled anymore.

Any suggestions why this happens?

@strothj
Copy link
Owner

strothj commented Oct 10, 2018

Hello,

Unfortunately monorepo support was dropped between the beta and final release. I added some information about the situation here:
#30

It should be possible to reproduce that monorepo support by reviewing the the changes in the files listed in that linked issue. The CRA team also outlined some alternatives.

@deftomat
Copy link
Author

deftomat commented Oct 11, 2018

Thank you for a detailed report in #30 👍

I think that it is time to create my own build config as CRA brings more harm than good for us. We always need to rewire it anyway 😞 .

I think that the biggest issue they have with a monorepo support is that they don't know if package should be transpiled or not. For TypeScript users, it's not a problem as we always need to transpile *.ts files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants