TypeScript is currently accepting contributions in the form of bug fixes. A bug must have an issue tracking it in the issue tracker that has been approved ("Milestone == Community") by the TypeScript team. Your pull request should include a link to the bug that you are fixing. If you've submitted a PR for a bug, please post a comment in the bug to avoid duplication of effort.

Features (things that add new or improved functionality to TypeScript) may be accepted, but will need to first be approved (marked as "Milestone == Community" by a TypeScript coordinator with the message "Approved") in the suggestion issue. Features with language design impact, or that are adequately satisfied with external tools, will not be accepted.

Design changes will not be accepted at this time. If you have a design change proposal, please log a suggestion issue.

You will need to complete a Contributor License Agreement (CLA). Briefly, this agreement testifies that you are granting us permission to use the submitted change according to the terms of the project's license, and that the work being submitted is under appropriate copyright.

Please submit a Contributor License Agreement (CLA) before submitting a pull request. You may visit https://cla.microsoft.com to sign digitally. Alternatively, download the agreement ([Microsoft Contribution License Agreement.docx](https://www.codeplex.com/Download?ProjectName=typescript&DownloadId=822190) or [Microsoft Contribution License Agreement.pdf](https://www.codeplex.com/Download?ProjectName=typescript&DownloadId=921298)), sign, scan, and email it back to <cla@microsoft.com>. Be sure to include your github user name along with the agreement. Once we have received the signed CLA, we'll review the request.

Your pull request should:

* Include a description of what your change intends to do

* To avoid line ending issues, set `autocrlf = input` and `whitespace = cr-at-eol` in your git configuration

jake runtests

You will probably only want to debug one test at a time:

**Note** that if you have a test corresponding to a specific spec compliance item, you can place it in `tests\cases\conformance` in an appropriately-named subfolder.

**Note** that filenames here must be distinct from all other compiler testcase names, so you may have to work a bit to find a unique name if it's something common.

One can also write a project test, but it is slightly more involved.

Compiler testcases generate baselines that track the emitted `.js`, the errors produced by the compiler, and the type of each expression in the file. Additionally, some testcases opt in to baselining the source map output.

When a change in the baselines is detected, the test will fail. To inspect changes vs the expected baselines, use

to establish the new baselines as the desired behavior. This will change the files in `tests\baselines\reference`, which should be included as part of your commit. It's important to carefully validate changes in the baselines.

return path.join(servicesDirectory, f);

"node.d.ts",

"editorServices.ts",

"protocol.d.ts",

"session.ts",

"server.ts"

].map(function (f) {

return path.join(serverDirectory, f);

var languageServiceLibrarySources = [

"editorServices.ts",

{ target: "lib.scriptHost.d.ts", sources: ["importcore.d.ts", "scriptHost.d.ts"], },

{ target: "lib.d.ts", sources: ["core.d.ts", "intl.d.ts", "dom.generated.d.ts", "webworker.importscripts.d.ts", "scriptHost.d.ts"], },

{ target: "lib.core.es6.d.ts", sources: ["core.d.ts", "es6.d.ts"]},

var libraryTargets = librarySourceMap.map(function (f) {

var processDiagnosticMessagesTs = path.join(scriptsDirectory, "processDiagnosticMessages.ts");

var diagnosticMessagesJson = path.join(compilerDirectory, "diagnosticMessages.json");

var diagnosticInfoMapTs = path.join(compilerDirectory, "diagnosticInformationMap.generated.ts");

ex.run();

}, {async: true});

task("generate-diagnostics", [diagnosticInfoMapTs]);

// Stanalone/web definition file using global 'ts' namespace

jake.cpR(standaloneDefinitionsFile, nodeDefinitionsFile, {silent: true});

var definitionFileContents = fs.readFileSync(nodeDefinitionsFile).toString();

// Official node package definition file, pointed to by 'typings' in package.json

// Created by appending 'export = ts;' at the end of the standalone file to turn it into an external module

}

cleanTestDirs();

var debug = process.env.debug || process.env.d;

tests = process.env.test || process.env.tests || process.env.t;

fs.unlinkSync(testConfigFile);

}

writeTestConfigFile(tests, light, testConfigFile);

}

colors = process.env.colors || process.env.color

colors = colors ? ' --no-colors ' : ' --colors ';

// timeout normally isn't necessary but Travis-CI has been timing out on compiler baselines occasionally

// default timeout is 2sec which really should be enough, but maybe we just need a small amount longer

});

});

}, {async: true});

var tslintRules = ([

"nextLineRule",

"noNullRule",

var tslintRulesFiles = tslintRules.map(function(p) {

return path.join(tslintRuleDir, p + ".ts");

});

task("lint", ["build-rules"], function() {

interface ArrayBufferConstructor {

prototype: ArrayBuffer;

new (byteLength: number): ArrayBuffer;

declare var ArrayBuffer: ArrayBufferConstructor;

interface ArrayBufferConstructor {

prototype: ArrayBuffer;

new (byteLength: number): ArrayBuffer;

declare var ArrayBuffer: ArrayBufferConstructor;