-
Notifications
You must be signed in to change notification settings - Fork 72
[Bug] Angular InstantSearch component does not work with Angular CLI v6 #90
Comments
Hi @prabh-62 Thank you for your feedback, I'm not sure what to do here since the CLI v6 is still in beta and will change. I'll wait for a RC before making changes to support the CLI v6. In the meantime I would recommend to stay with the v1.x |
And thank you to pointing me directly to the comment, this is the root cause about |
!!process && .... should probably do the trick to fix this. |
Yes, but the use of process here is in a downstream dependency. It would probably be best to add the serialising of process.env in your angular settings for now to make sure no error happens |
This bug still exists and it's a problem |
See algolia/algoliasearch-client-javascript#692 and algolia/algoliasearch-client-javascript#691. Could you try that out or give a reproducible project please? |
My PR to the API client was insufficient due to some complications with our build process, but the workaround you can use in your app is adding this to (window as any).process = {
env: { DEBUG: undefined },
}; |
@Haroenv awesome this works that's good enough for me thanks! |
Angular InstantSearch v2.0.0 is released, you can now use Angular v6.0.0 with the This is documented on the Getting started and Migration guide |
I'm submitting a...
Current behavior
Algolia InstantSearch Angular component does not work with Angular CLI v6
Expected behavior
Algolia InstantSearch Angular component should work with Angular CLI v6
Minimal reproduction of the problem with instructions
Open Chrome browser and enable devtools. We receive an error "process is not defined" in Console
Apparently, there was a breaking change in Angular CLI - Read this Comment
Reference: angular/angular-cli#9827
Environment
Package versions:
Browser:
System:
The text was updated successfully, but these errors were encountered: