[meta-issue] add Blocking Proxy

[juliemr]

Collecting issues that we'll need to reconsider (usually, because they'll be easier/improved) when we switch over to Blocking Proxy.

Background: Blocking Proxy is our plan to move logic that waits for Angular to stabilize into a separate process, a proxy which lives between the test script and the selenium endpoint, and intercept the JSON WebDriver protocol commands.

[juliemr]

We can do better logging - #2569

[juliemr]

#2986

[juliemr]

Note that this will be available in 5.0 behind a flag.

[karlhaas]

not sure if this is the right place but after upgrading to protractor v5.1.0 typescript reports the following error:
node_modules/blocking-proxy/built/lib/blockingproxy.d.ts(6,32): error TS1039: Initializers are not allowed in ambient contexts.
typescript version: 2.0.10

[heathkit]

Blocking Proxy is built with TypeScript 2.1, which is what's generating that definition file. If you do npm upgrade to get the latest version of Protractor's dependencies, you should get TS 2.1 and that error will go away.

[karlhaas]

thx @mgiambalvo! This means that TS2.1 is required for the current version of Protractor, right? if so, it should maybe be mentioned in the list of breaking changes.

[karlhaas]

After upgrading TS, AoT does not work.

Error: Error encountered resolving symbol values statically. Could not resolve events relative to projectdir/node_modules/blocking-proxy/built/lib/webdriver_commands.d.ts., resolving symbol WebDriverCommand in projectdir/node_modules/blocking-proxy/built/lib/webdriver_commands.d.ts
    at simplifyInContext (projectdir/node_modules/@angular/compiler/bundles/compiler.umd.js:25795:27)
    at StaticReflector.simplify (projectdir/node_modules/@angular/compiler/bundles/compiler.umd.js:25807:17)
    at StaticReflector.annotations (projectdir/node_modules/@angular/compiler/bundles/compiler.umd.js:25299:84)
    at NgModuleResolver.resolve (projectdir/node_modules/@angular/compiler/bundles/compiler.umd.js:17783:86)
    at CompileMetadataResolver.getNgModuleMetadata (projectdir/node_modules/@angular/compiler/bundles/compiler.umd.js:18284:64)
    at addNgModule (projectdir/node_modules/@angular/compiler/bundles/compiler.umd.js:25065:62)
    at projectdir/node_modules/@angular/compiler/bundles/compiler.umd.js:25076:18
    at Array.forEach (native)
    at _createNgModules (projectdir/node_modules/@angular/compiler/bundles/compiler.umd.js:25075:30)
    at analyzeNgModules (projectdir/node_modules/@angular/compiler/bundles/compiler.umd.js:24950:18)
Compilation failed

[heathkit]

Ah, that's indeed the case. Angular doesn't support TS 2.1 yet (angular/angular#13294). Sorry about that, making Protractor require TS 2.1 wasn't intentional breaking change. I'll try to get a hotfix out soon that uses a version of blocking-proxy built with TS 2.0.