No provider for ORIGIN_URL about universal-starter

[Gorniv]

'node server.js' dont use prerender. Prerender is alternative for use static with seo and angular.
Look https://github.com/AngularClass/universal-sitegen

[Gorniv]

fix it 3d589fc

[asadsahi]

@Gorniv thank, it has indeed. What pattern do you reckon about generating these pre-rendered pages? during development or production. Hardcoding URL suggest that we need to host the url because if pages use any http request to get data, pre-render fails since it cannot find any site on that url yet.

When deployed on production, url will exist so pre-render can get the data. Also have you given any thoughts on caching strategy of dynamic or pre-renderd page? what are the options?

[Gorniv]

Prerender build pages with all content one time. Value of ORIGIN_URL depends on your page and logic. You use angular with current ORIGIN_URL of web browser page after prerender. I think that prerender page needs a very simple site like landing. I use dynamic server-side render with node.

[asadsahi]

@Gorniv in your case you aren't using ORIGIN_URL during SSR/Prerender but in my case I get some data fetched from server when application initialises, therefore in order to build these pre-rendered pages, I have to make a working ORIGIN_URL. And it works if I have ORIGIN_URL serving the data.

Having site pre-rendered already for all urls surely boost performance since there isn't any server side execution.

Does following code works for both pre-rendering and dynamic rendering?

 const { AppServerModuleNgFactory, LAZY_MODULE_MAP } = require(`./dist/server/main.bundle`);
      this.app.engine('html', ngExpressEngine({
        bootstrap: AppServerModuleNgFactory,
        providers: [
          provideModuleMap(LAZY_MODULE_MAP)
        ]
      }));

Does it try to get pre-render page and then falls back to dynamic rendering?

[Gorniv]

@asadsahi if you want to use prerender and dynamic rendering you need change server.ts. Server.ts need use a different route for prerendering and dynamic route. I will think about add example in the repository.
I add environment in prerender.ts

[asadsahi]

@Gorniv If you don't generate prerender pages then existing setup does dynamic rendering. I am not using 100% your server.ts and prerender.ts but I think ngExpressEngine falls back to dynamic rendering if prerender pages aren't found.

Your setup matches quite close to angular-universal starter and thats what I am following and just proved the concept described above.

[asadsahi]

Ahh I see, so does that mean with current setup it always use dynamic-rendering? pre-render pages are only if someone wants to use static pages?

[Gorniv]

@asadsahi yes, subscribe to #8

[asadsahi]

Thanks @Gorniv