-
Notifications
You must be signed in to change notification settings - Fork 601
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
By compiling using build --prod I get an error when trying to load layer from URL option, this is happening to me on master or develop branches #334
Comments
That's not an error I've seen before. I don't think this is caused by trying to load a layer by URL since it occurs when importing the initial ATT&CK data (in getDomainData). From the error it looks like Did you Another possibility is that the import of
and then invoke as:
But the docs of RxJS import it like this:
It's possible that the way we're using it is no longer supported. |
Hi @isaisabel, thanks for you quick reply!, in angular.json if I turn off AOT feat then everything works as expected from build --prod this is what I'm currently using for getting it works :
the point is if I revert this and set as it comes as default, and just make build not(--prod) no errors related about 'forkJoin' is displayed |
That's actually consistent with how we build the live deployment of the Navigator now that I look at my notes. We build with the following:
I can't remember if we ever tracked down the cause. I'll leave this issue open to document the fact that we should probably track it down and document it. In the meantime I'll amend the docs to clarify that |
mmm...OK ok, yep It would be nice having the docs updated with that clarification. Have a nice day. |
Greetings! We have run into this issue, too. Luckily it was already raised! I have also seen that it is in the documentation. (too late! :P) ng build --prod without the extra flags raises errors with forkJoin when trying to fetch data from URL. Adding the flags, works as expected. Thanks for your help. Have a nice day! |
The text was updated successfully, but these errors were encountered: