-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Error: No component factory found for NbSearchFieldComponent. #402
Comments
@yggg did you have any similar issues working on SSR? |
@denisobrienirl Did you find a solution in the end ? |
@somq No, sir. I have not followed this issue through. It doesn't seem to affect my application at all, so no major focus given. Sorry, can't be more helpful. |
@denisobrienirl alright, thanks for your answer anyway.
This is the weird thing here, I'm getting this error about the |
@nnixaa Hi Dmitry, Feel free to close this issue. I don't think it's relevant anymore. Cheers, |
ah, damn it... posted under wrong ID... apologies, but the same stands... it's no longer an issue... |
@denisobrienirl no problem! |
Issue type
I'm submitting a ...
Issue description
Current behavior:
Running compiled(AOT) universal app based on bare bone Nebular UI Started Kit (no major modifications to the default provided code), triggers an error below:
I have not made any changes to nb-search component, the only reference that exist to it in the project is in the default search action in the ngx-admin header component.
Expected behavior:
No error should be triggered.
Steps to reproduce:
I have built the app using the following tutorial - https://angular.io/guide/universal. There were some issues during the compilation process, but all have been addressed and seem irrelevant to the error message above.
Once the application is launched with 'npm serve:universal' script(as per tutorial), it launches express server and starts the app (no errors at this stage yet).
First attempt to access the app with any browser, spawns the error message mentioned above.
P.S. Interesting to note, that navigating through the app after the initial load does not trigger the error message. Only if a new session started (new tab or new browser used), it triggers the error message again.
Related code:
I'm not quite sure what code is relevant to this issue, but here is an extract from the error message referencing Nebular UI internal logic:
For what it's worth, here's my server.ts. Again, not sure it's relevant in this case, but that's the module that controls SSR (the initial rendering of the content on first request to the app).
Other information:
npm, node, OS, Browser
Angular, Nebular
The text was updated successfully, but these errors were encountered: