ts-mocha | Mocha thin wrapper that allows running TypeScript tests | Runtime Evironment library

Turns out none of the package.json config options were working for me. I wound up implementing a .mocharc.json on the same level as my package.json which worked perfectly.

Example from this github repo (with more examples) copied here for posterity.

you can add the following configuration to tsconfig.json file.

You need to tell the compiler to watch for changes. Add the following script or adjust your compile script with the watch flag:

I found the solution myself.

While debugging my tests I discovered that some of the exports are not being called. This is due to cyclic dependencies of the files, that prevented them from being exported correctly.

After finding these cycles using https://github.com/pahen/madge and resolving them, running tests is working just fine.

Okay so turns out it was because my shell environment was different for yarn.

I ran the following to fix it as I use fish for my shell.

yarn config set script-shell "/usr/local/bin/fish"

I noticed that the CircleCI NODE_ENV environment variable was set to production, therefore any devDependencies were not getting installed (even with npm install --save, because it was already listed as a devDependency in the package.json).

I don't know when the environment variable was changed to that value, but the odd thing is that it started breaking from one day to another (although it should've been breaking since the moment that env variable was set) so it was extremely hard to debug, but it was a simple fix: changing the NODE_ENV environment variable in CircleCI to something different than production.

Ok, I have got it to work.

This is, what I have done:

tsconfig.json:

Add

I can fix one bug,but another one I don't know how to fixed,because I can't found the primitive type for such type.because type is only exists in typescript,in javascript there is no type.the type of String is not reference to javascript String class,if you want let typescript compile correctly you must use string in type sides.like foo:string nor foo:String;when you write let string: String = String; the compiler report errors,because left side ref a type,the right side ref a String constructor,they are different.I'm sorry,I'm not good english,so I wish you could understand what I was said.unimaginable,the typescript compiler will compile the String type into String class into .js file,you can use tsc compile the js file and see result.the 3rd test could be run,I think user defined class play the two roles:the instance of the class & the type of the class.but Date & String separate type/constructor functioninto two parts: type as an interface 'String',constructor function via global variable StringConstructor