You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
JavaScript in TypeScript compilations (See parent issue #4789 for an overview) There are a number of considerations for the TypeScript compiler to handle JavaScript code: Should the compiler automatically pick up JavaScript files in a folder as it does for TypeScript? If so, how to avoid compiling JavaScript files that were emitted by a prior TypeScript compilation? Should the compiler emit JavaSc
N.B. these notes use the word "module" extensively, which we now use to only mean "external module" in the old parlance. I will use "namespace" to refer to "internal modules" if needed. Augmenting Types from External Modules (#5269, #4166) Bind operator is like extension methods for JS But people do love . And if you love .., prototype mutation is the only way to accomplish it Two problems facing
This issue describes TypeScript's support for ECMAScript 6 modules as implemented in #1983, #2197, and #2460. TypeScript 1.5 supports ECMAScript 6 (ES6) modules. ES6 modules are effectively TypeScript external modules with a new syntax: ES6 modules are separately loaded source files that possibly import other modules and provide a number of externally accessible exports. ES6 modules feature severa
For various reasons that are discussed in other issues, some people like to pipe TS into Babel for the downlevel (e.g. ES5) code generation. I won't reiterate here why one might want to do so. Now that TS is starting to get ES7+ features such as async, decorators, possibly :: & co. it would be very welcome to add a ES7 (ES2016) target. The use case today is to get raw, non transformed code from TS
Summary Implement annotations in TypeScript. Align with Traceur and AtScript on syntax and ES5 representation. Implement feature similarly to modules, with the following settings for output representation: -annotations=none (default) - Annotations not supported by default. Produce compiler errors when used. -annotations=atscript - Annotations encoded in the style of traceur/atscript (this proposal
Aims We are delivering a plugin-based application framework as part of PhosphorJS; the idea being that any application can be easily extended, statically or at runtime, by adding a new plugin. This brings with it a range of issues, with front-end packaging being one of the most important. Unfortunately, front-end packaging in javascript is widely regarded as a minefield. There are a number of opti
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く