update to rc5/rc6/rc7

[PatrickJS]

rc6/rc7 update

• create NodeDomEventsPlugin from DomEventsPlugin
• create NodeEventManager from NodeEventManager
• recreate DomRenderer for NodeDomRenderer
• recreate SharedStylesHost for NodeSharedStylesHost
• recreate Parse5DomAdapter with parse5 2.x.x
• fix the events that were coupled to Parse5DomAdapter and one document
• making sure the pipeline is as fast as possible outside of the angular's internal bootstrap
• decouple the universal rendering pipeline for scheduling
• inject latest version of preboot
• create a way to dehydrate data from server to client via UNIVERSAL_CACHE
• allow APP_ID to be passed to client to reuse styles
• include lifecycle hooks for NodePlatform
  • universalOnInit
  • universalDoCheck
  • universalOnStable
  • universalDoDehydrate
  • universalAfterDehydrate
  • universalOnRendered
• move most NodePlatform logic to UniversalPlatform
• reuse NodeModule as UniversalModule
• create initial UniversalPlatform
• initial UniversalModule for browser
• UniversalModule for Browser
  • create lifecycle hooks
  • link APP_ID to reuse styles
  • link preboot
  • link http resources made from the server to the client for prime cache mode
  • link hydrate resources
• recreate integrations
  • angular2-express-engine
  • angular2-hapi-engine
  • angular2-webpack-prerender
  • angular2-gulp-prerender
  • angular2-grunt-prerender
• fix publishing packages
• use Zone.js for context config

after initial release

• allow canceling requests
• include fixed preboot version
  • auto include appRoots
  • inject at last entryComponent
• perf tests
• recreate Bootloader as Universal to manage concurrent apps and app lifecycles with middleware
• move most serialize logic from NodePlatform to Universal
• update integrations with full app with routes prerendering support
• write about auth management
• write about state/resource/cache management server/client/both
• write about pm2 and cluster management
• write about best practices
• get AoT compiler working
• patch zone.js for http/https WIP feat(node): patch outgoing http requests to capture the zone zone.js#430
• patch zone.js for fs feat(node): patch most fs methods zone.js#438
• update universal services design

experimental

• include a webpack universal-loader for prerendering
• create new universal prerender solution
• section off pages for prerender and rerender for fastest server rendering solution

[maciejtreder]

Any forecast when you are going to implement this?

[lmantis]

Hi, I would like to know too. Thanks in advance.

[PatrickJS]

here's a preview of what I have so far which is sticking to the angular API as much as possible

import { NgModule } from '@angular/core';
import {
  NodeModule,
  NodeHttpModule,
  NodeJsonpModule,
  platformDynamicNode,
} from '@angular/universal';

import { App } from './app';


export const platform = platformDynamicUniversal();

export function main(document) {

  @NgModule({
    bootstrap: [ App ],
    declarations: [ App ],
    imports: [
      UniversalModule.forRoot(document, {
        originUrl: 'http://localhost:3000',
        baseUrl: '/',
        requestUrl: '/'
      }),
      NodeHttpModule,
      NodeJsonpModule
    ],
    providers: [ ]
  })
  class MainModule {}

  return platform
    .serializeModule(MainModule)
    .then((html) => {
      console.log('done')
      return html
    });
};

[GrandSchtroumpf]

Is '@angular/universal' released yet ? I can't get my hand on it with npm.

[maciejtreder]

@GrandSchtroumpf
On my end it's working:

npm install angular2-universal@0.104.5

This is latest version. But it is not working with latest angular (rc.5).

I believe that if you want to use it with rc.5 solution provided by @gdi2290 is working correctly (I did not check it no my end).

[PatrickJS]

rc.5 is not released yet for universal

[maciejtreder]

@gdi2290

So code which you provided is not compatible with angular rc5? Do I understand correctly?

[PatrickJS]

the current API is compatible but will be depreciated since I was essentially doing what NgModule now allows me to do. The rc5 release of universal will recommend users to follow the Angular API conventions.

The old Bootloader API will still be supported until everyone switches to the new NgModule syntax using UniversalModule. The benefits of the new API allows me to provide server-only-components in any other part of the component tree rather than only being limited to the parent of the root component tree