Use PnP aware Yarn in CI.

[rwjblue]

No description provided.

[stefanpenner]

Thanks for the fix.
It also seems like the test passes on my machine with 10.9, and fails with 11.9. Could be my 10.9 environment is hosed?

[stefanpenner]

I suspect the yarn version in windows is old, let me bump it

[stefanpenner]

let's see if this works

[stefanpenner]

Ok that got us 1 step closer

'require(resolve-package-path)(ember-source-channel-url,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
SyntaxError: Invalid or unexpected token
    at createScript (vm.js:80:10)
    at Object.runInThisContext (vm.js:139:10)
    at Object.<anonymous> ([eval]-wrapper:6:22)
    at Module._compile (module.js:653:30)
    at evalScript (bootstrap_node.js:479:27)
    at startup (bootstrap_node.js:180:9)
    at bootstrap_node.js:625:3
error Command failed with exit code 1.
$ node -r ./.pnp.js -e 'require("resolve-package-path")("ember-source-channel-url", __dirname)'

windows escaping FTL, going to move that test into its own file.

[stefanpenner]

released as v1.0.3 🎉

[davecombs]

🎉 !

[rwjblue]

@stefanpenner the reason Node 10 worked without this change, but Node 11 required it is due to a change (probably a bug?) in how Node 11 parses NODE_OPTIONS.

See:

• Change in NODE_OPTIONS parsing behavior in Node 11 nodejs/node#26521
• Plug'n'Play does not work with Node 11 yarnpkg/yarn#7092

[stefanpenner]

Looks like node folks fixed this in 11.12.0