fix(platform-node): 2.1.1 fix - update private imports and make backwards compatible

[MarkPieszak]

Fixes #606

SelectorMatcher & CssSelector made public.

ViewUtils changed to view_utils

Backwards compatibility

[PatrickJS]

this also needs to be backwards compatible

[John0x]

Anything new regarding this issue?

[MarkPieszak]

@gdi2290 want me to refactor this more in your way?

[qibucloud]

Angular2 在 asp.net core 里面只能这样使用？ 不能官方原生态使用？

Angular2 in asp.net core which can only be used? Can not the official use of the original ecology?

[SamD]

Any update, not seeing the fix applied. The latest npm version is 2.1.0-rc.1

[MarkPieszak]

@SamD @julienR2 I believe we need to wait for Core to make these changes, but in the meantime if you want to use 2.1.1+ you can use the __2.1.1.workaround.ts file: https://github.com/MarkPieszak/aspnetcore-angular2-universal/tree/master/Client here, and then include it in both the client & server bootstrap files. That can at least hold you off for now!

[julienR2]

Thanks a lot for the workaround ! I missed it during my investigations.. Not in a hurry for 2.1.1+ so far, but I keep it close in case I need a feature from this version until Core changes :)

[larsbeck]

@MarkPieszak I tried this workaround with 2.2.0, but it doesn't seem to do the trick. Should it work with 2.2.0 as well?

[MarkPieszak]

@larsbeck use the workaround fix here (https://github.com/MarkPieszak/aspnetcore-angular2-universal/tree/master/Client) take the workaround file put it in your project and import it to the top of your client & server main files.

import './__2.1.1.workaround.ts'; // temporary until 2.1.1 things are patched in Core

[larsbeck]

@MarkPieszak Ah yes, moving them to the very top fixed it. Thanks!

[PatrickJS]

this gets really tricky to support semver. It's best just to follow the angular releases for at least the major and minor releases while the patches we can release out of sync

[Reuvenc]

Is there anything new regarding this PR?
I'm trying to integrate AOT for universal, but although using the workarounds provided in universal-starter repo, I'm still getting SelectorMetcher errors (SelectorMatcher of undefined).

[PatrickJS]

will be fixed in ng4
angular/angular#13822

[sohaibjaved44]

People who are planning to import "import './__2.1.1.workaround.ts'; " need to take care of the order as well.
Some people have mentioned that it is supposed to be placed after pollyfills but in my case it was happy at 3rd place after polyfills and @angular/core... Hope it help someone.
import 'angular2-universal-polyfills/browser';
import { enableProdMode } from '@angular/core';
import './__2.1.1.workaround.ts';

[MarkPieszak]

Yes @sohaibjaved44 typically you want it below the universal polyfills, otherwise some bizarre errors pop up.

[daveriedstra]

@MarkPieszak and @sohaibjaved44 thank you! This fixed something that's been confusing me for hours. I think I was confused because of this comment.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}