npm run testexpected to run locally? Wondering why is it breaking at "karma:unit:ChromeHeadless"? Below is the message what i get
Running "strip_code:debug" (strip_code) task Running "strip_code:prod" (strip_code) task Running "karma:unit:ChromeHeadless" (karma) task 05 10 2018 11:16:34.172:WARN [watcher]: Pattern "/Users/apple/projects/boomerang/tests/vendor/mocha/mocha.css" does not match any file. 05 10 2018 11:16:34.174:WARN [watcher]: Pattern "/Users/apple/projects/boomerang/tests/vendor/mocha/mocha.js" does not match any file. 05 10 2018 11:16:34.175:WARN [watcher]: Pattern "/Users/apple/projects/boomerang/tests/vendor/assertive-chai/dist/assertive-chai.js" does not match any file. 05 10 2018 11:16:34.210:INFO [karma]: Karma v1.7.1 server started at http://0.0.0.0:4000/ 05 10 2018 11:16:34.211:INFO [launcher]: Launching browser ChromeHeadless with unlimited concurrency 05 10 2018 11:16:34.215:INFO [launcher]: Starting browser ChromeHeadless 05 10 2018 11:16:34.716:INFO [HeadlessChrome 69.0.3497 (Mac OS X 10.14.0)]: Connected on socket vDRuKUkbdmMr8hn0AAAA with id 41279479 HeadlessChrome 69.0.3497 (Mac OS X 10.14.0) ERROR Uncaught ReferenceError: chai is not defined at unit/00-logging.js:5 HeadlessChrome 69.0.3497 (Mac OS X 10.14.0) ERROR Uncaught ReferenceError: chai is not defined at unit/00-logging.js:5 1..0 05 10 2018 11:16:34.833:INFO [karma-tap-reporter]: writing report to file: /Users/apple/projects/boomerang/tests/results/unit.tap Warning: Task "karma:unit:ChromeHeadless" failed. Use --force to continue. Aborted due to warnings. npm ERR! Test failed. See above for more details.
c.ttiregardless of the value of
spa.hardevent firing with a react app
Sorry one more question @andreas-marschke I have a react app which on load typically:
1) Loads a bundle
2) Shows a nav bar and loading spinner while it does an initial graphql call
3) Once the graphql completes shows the main content
Currently it seems like
spa events wait for the graphql call to finish but not
spa_hard events. Is it possible to get both to wait? Our page isn't really usable until the call finishes. Thanks!
@gregology I am not aware of such implementation but migrating it to Python should be an easy task. Here I ported the decompressor to PHP for about 4 hours: https://github.com/revampix/boomerang-resourcetiming-decompression-php-port/blob/master/resourcetimingDecompression.0.3.4.php
P.S. At the moment of porting I had not much experience with JS. If you are going to port it then use some kind of automated testing. I found it useful to test with input JSON resource timing string and compare the final output/result with pre-generated output taken from the JS implementation. Ref: https://github.com/revampix/boomerang-resourcetiming-decompression-php-port/blob/master/test/resourcetimingDecompressionTest.0.3.4.php