i tried it out and removed everything. karma, chrome, jasmine.
syntax is marginally different, now it's expect(something).to.be.null instead of .to.be(null)
that’s fine if it makes testing easier :)
could even have it run tests on watch now
hehe
yes, that's what i have my BDD watcher task for.
if it doesn’t we could create an issue
that guy is really good about it
build, watch and watch-test should do as little work as possible.
although, do we have to transpile for tests?
I think that’s a yes
at least, that's what i imagine right now
yes, we need to transpile, and with source maps so.
because it will make debugging much easier. i've enabled source maps in karma, so we get stack traces with actual typescript references
no more searching in js files
it also enables stepping into typescript. i didn't get that with our current solution, sadly
well we have the build step
which publish relies on
so we should be fine. unless all of that changed
with gulp-tsb and incremental builds i got it down to 0.5 seconds when a file changes.
that should make it faster no?
yes, but even that could be included in watch
and even before building, because, i don't want to build if my source code has errors
i'll try to get incremental builds working with tsproject
but first, i fix stringify
#36 has been rebased onto all commits that have happened in the meantime
should be ready for merge