Running tests in nwjs results in testing attempting to use aurelia-pal-nodejs
timfish opened this issue · comments
I'm submitting a bug report
- Library Version:
1.0.0-beta.2.0.1
Please tell us about your environment:
- Windows 10
- node 6.6.x
- JSPM 0.16.32
-
Browser:
Chrome AND nwjs -
Language:
TypeScript
Current behavior:
Tests run fine in Chrome. I have converted to running tests in nwjs as this is the platform the code will actually run on. If I have any tests using aurelia-testing I get an error:
[16:50:12] Starting 'tdd'...
13 12 2016 16:50:14.448:WARN [karma]: No captured browser, open http://localhost:9876/
13 12 2016 16:50:14.483:INFO [karma]: Karma v1.3.0 server started at http://localhost:9876/
13 12 2016 16:50:14.484:INFO [launcher]: Launching browser NodeWebkit with unlimited concurrency
13 12 2016 16:50:14.488:INFO [launcher]: Starting browser node-webkit
13 12 2016 16:50:16.915:INFO [Chrome 54.0.2840 (Windows 10 0.0.0)]: Connected on socket /#2i23ZR1asgqFp6m3AAAA with id 66075243
Chrome 54.0.2840 (Windows 10 0.0.0): Executed 0 of 54 SUCCESS (0 secs / 0 secs)
ERROR: 'Potentially unhandled rejection [3] (SystemJS) XHR error (404 Not Found) loading http://localhost:9876/base/aurelia-pal-nodejs.js
Error: XHR error (404 Not Found) loading http://localhost:9876/base/aurelia-pal-nodejs.js
Error loading http://localhost:9876/base/aurelia-pal-nodejs.js'
Expected/desired behavior:
When running the tests in nwjs, it should run the tests in the same way as in Chrome. Does the PAL detection work by detecting the presence of the node process variable?
Actually, this might be an issue with the bootstrapper v2 as updating that has stopped my entire app from running in nwjs!
Caused by updating to bootstrapper v2 but the bug could be somewhere in the pal detection.