tsc

On my website I want to import a FancyModule using SystemJS , so that I can create instances of classes which this module exports. So what I want to achieve is this (within a ECMAScript 2015-compatible website): SystemJS.import('MyFancyModule').then(function(MyFancyModule) { var myFancyInstance = new MyFancyModule.MyFancyClass('Test'); console.log(myFancyInstance.text); }); Unfortunately, I am getting the following error: TypeError: MyFancyModule.MyFancyClass is not a constructor(…) Here is my TypeScript module: export module MyFancyModule { export class MyFancyClass { public text: string;

I have the following settings in the tsconfig.json . I added "es2017" to use Array.includes .: { "compilerOptions": { "lib": [ "es6", "es2017", "dom" ], "module": "es6", "target": "es5" } } Now, I realized, that I have to add import 'core-js/es7/array'; to the polyfills.ts , to use Array.includes also for the Internet Explorer 11. The target in the tsconfig.json is set to es5 , which does not have Array.includes . Why do I need to add the polyfill? TypeScript does not auto-polyfill code. The "official" reason from the relevant GitHub issue seems to be, as @RyanCavanaugh said : Having the

1.首先查看自己电脑CPU是否支持虚拟化： grep - E "vmx|svm" /proc/cpuinfo 如果打印结果像下面一样又臭又长： flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3 dnowprefetch epb intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep

I like to have my comments intact in the resulting javascript file, by default the compiler removes them. Is there a tsc parameter for that? (The use case is to keep /// reference path's = ... for chutzpah unit testing. ) Yes, the -c (or --comments) option; Syntax: tsc [options] [file ..] Examples: tsc hello.ts tsc --out foo.js foo.ts tsc @args.txt Options: -c, --comments Emit comments to output ... Comments that start with /*! are preserved. example: /*! this comment remains untouched */ /* but this one will be removed */ Imanou Petit Since 2015 you can create a tsconfig.json in your project

I can't seem to get the outDir flag working when used in package.json . Directory structure is pretty simple: tsconfig.json at the root level, together with a src/ directory and a single index.ts file plus other directories representing other modules. When running the tsc command on the index file, it creates a new one beside it instead of in the build directory. What am I doing wrong? My tsconfig: { "compilerOptions": { "outDir": "build" } } My npm build script: "build": "tsc src/index.ts" I'm calling the script from the root dir of the project. Interestingly, running the same script with an

I am trying to run the TypeScript compiler from my Java application. To start, I am trying to figure out, whether I can run the compiler from command-line without Node.js: $ jsc tsc.js But this way I don't get any errors, nor help. $ jsc tsc.js myscript.ts Will get me nowhere. It is easy to run js code directly from java (and I am hoping to run the compiler in this way), but is it possible to run TypeScript compiler without node.js? EDIT: I confirm the same behaviour with rhino. Looking at the source code, the tsc command invokes a JS script tsc.js , which has 2 backends: Node.js and Windows

I found a problem in my app structure and build process using WebPack, TypeScript, and TS-Loader that I thought was caused by TypeScript 2.1.4, but apparently was there the whole time. You can see all the details from my other post: TypeScript 2.1.4 breaking changes in webpack ts-loader In short, I have Gulp and WebPack set to an entry point of /client/app.ts which for now has almost nothing in it (certainly nothing referencing /server/) but the TypeScript compilation stage of the WebPack build process is still trying to run on /server (and in my other post, showing a compilation error from

Is there a way to mute the TS2307 error from the TypeScript tsc compiler? It makes it really hard to spot real/new errors and warnings as there are many TS2307 errors in our codebase. Update : This error occurs when an external module is import ed without its type definition .d.ts being present. I'm aware of tsd but for many libraries we use, no type definitions exist. No, there is not a way to direct the compiler to suppress TS2307. There has been some discussion about it for exactly the reason you describe. For large projects, this becomes a huge barrier to entry. Details here: Making