johnjbarton
johnjbarton
I guess I needed to use a v0.4 tag in node
> Karma serves all files from localhost:[port]/base/. I missing something really basic in the config for karma-systemjs: how to I serve my test files located in `/test`?
Yes, unifying on that form. But also deprecating and removing the function parsing thing https://github.com/vojtajina/node-di/blob/master/lib/annotation.js
I don't know what background you are looking at but try: http://karma-runner.github.io/5.2/dev/contributing.html
@alexanderby We have the docs in dark mode so a PR to change the test page would be welcome.
I suggest trying to run the test locally so you can use --noSingleRun then use the browser's debug tools to figure out how the document is getting mutated.
Just add some console.log('xxxxxxxxxxxxx') calls in the file and in each function to see if the code is even executed.
Another debugging suggestion is to run with `--logLevel=debug`. At what point do the `.ts` files get compiled to `.js`?
Based on what I see here, I would reach a different conclusion: no matter what kind of preprocessing we apply to TypeScript files, the browser will not be able to...
We hit the same issue. I wonder if we can use `--` testFiles and change our karma.conf.js to look in `process.argv._`? https://github.com/yargs/yargs/blob/HEAD/docs/tricks.md#stop-parsing