Skip to content
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

Cannot build 1 of 3 apps after upgrading to NX 0.54 and app level tsconfig files #169

Closed
thaoula opened this issue Dec 20, 2017 · 2 comments

Comments

@thaoula
Copy link

thaoula commented Dec 20, 2017

Hi Guys,

Got a very strange situation where after upgrading to 0.54 and moving to app based tsconfig files we are unable to AOT build 1 app from 3.

We can build the APP without AOT and it builds fine. However, when building the APP with --prod the build fails whilst reporting several components in a different app not being part of an Ngmodule.

The components that are broken belong to the AppModule of a different app. The weirdest thing is that the error is not for all the components in the other AppModule its for only 4/6.

So in summary,

  • We are using Angular 5.1, Angular CLI (release16), NX 0.54.
  • The tsconfig.app are the defaults created by nx-migrate.
  • All apps except the one can be built using AOT.
  • All apps can build without AOT
  • We can build the app using AOT if we revert the app back to using the parent tsconfig.

We have been trying to track down this issue for 4 days. Ran out of ideas and was wondering if someone has seen something like this before.

Regards,
Tarek

@thaoula
Copy link
Author

thaoula commented Dec 22, 2017

Guys,

I think this is user error. We found an incorrect import.

Regards,
Tarek

@thaoula thaoula closed this as completed Dec 22, 2017
FrozenPandaz added a commit to FrozenPandaz/nx that referenced this issue Jan 12, 2023
@github-actions
Copy link

This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants