PageRenderTime 27ms CodeModel.GetById 25ms RepoModel.GetById 0ms app.codeStats 0ms

/frontend/node_modules/@angular-devkit/build-optimizer/node_modules/typescript/README.md

https://gitlab.com/girmayegebremedhin/student_managment
Markdown | 107 lines | 77 code | 30 blank | 0 comment | 0 complexity | af9695ab68b277f099c78feb76744480 MD5 | raw file
  1. # TypeScript
  2. [![Build Status](https://travis-ci.org/microsoft/TypeScript.svg?branch=master)](https://travis-ci.org/microsoft/TypeScript)
  3. [![Devops Build Status](https://dev.azure.com/typescript/TypeScript/_apis/build/status/Typescript/node10)](https://dev.azure.com/typescript/TypeScript/_build?definitionId=7)
  4. [![npm version](https://badge.fury.io/js/typescript.svg)](https://www.npmjs.com/package/typescript)
  5. [![Downloads](https://img.shields.io/npm/dm/typescript.svg)](https://www.npmjs.com/package/typescript)
  6. [TypeScript](https://www.typescriptlang.org/) is a language for application-scale JavaScript. TypeScript adds optional types to JavaScript that support tools for large-scale JavaScript applications for any browser, for any host, on any OS. TypeScript compiles to readable, standards-based JavaScript. Try it out at the [playground](https://www.typescriptlang.org/play/), and stay up to date via [our blog](https://blogs.msdn.microsoft.com/typescript) and [Twitter account](https://twitter.com/typescript).
  7. Find others who are using TypeScript at [our community page](https://www.typescriptlang.org/community/).
  8. ## Installing
  9. For the latest stable version:
  10. ```bash
  11. npm install -g typescript
  12. ```
  13. For our nightly builds:
  14. ```bash
  15. npm install -g typescript@next
  16. ```
  17. ## Contribute
  18. There are many ways to [contribute](https://github.com/microsoft/TypeScript/blob/master/CONTRIBUTING.md) to TypeScript.
  19. * [Submit bugs](https://github.com/microsoft/TypeScript/issues) and help us verify fixes as they are checked in.
  20. * Review the [source code changes](https://github.com/microsoft/TypeScript/pulls).
  21. * Engage with other TypeScript users and developers on [StackOverflow](https://stackoverflow.com/questions/tagged/typescript).
  22. * Help each other in the [TypeScript Community Discord](https://discord.gg/typescript).
  23. * Join the [#typescript](https://twitter.com/search?q=%23TypeScript) discussion on Twitter.
  24. * [Contribute bug fixes](https://github.com/microsoft/TypeScript/blob/master/CONTRIBUTING.md).
  25. * Read the language specification ([docx](https://github.com/microsoft/TypeScript/blob/master/doc/TypeScript%20Language%20Specification.docx?raw=true),
  26. [pdf](https://github.com/microsoft/TypeScript/blob/master/doc/TypeScript%20Language%20Specification.pdf?raw=true), [md](https://github.com/microsoft/TypeScript/blob/master/doc/spec.md)).
  27. This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see
  28. the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com)
  29. with any additional questions or comments.
  30. ## Documentation
  31. * [TypeScript in 5 minutes](https://www.typescriptlang.org/docs/handbook/typescript-in-5-minutes.html)
  32. * [Programming handbook](https://www.typescriptlang.org/docs/handbook/basic-types.html)
  33. * [Language specification](https://github.com/microsoft/TypeScript/blob/master/doc/spec.md)
  34. * [Homepage](https://www.typescriptlang.org/)
  35. ## Building
  36. In order to build the TypeScript compiler, ensure that you have [Git](https://git-scm.com/downloads) and [Node.js](https://nodejs.org/) installed.
  37. Clone a copy of the repo:
  38. ```bash
  39. git clone https://github.com/microsoft/TypeScript.git
  40. ```
  41. Change to the TypeScript directory:
  42. ```bash
  43. cd TypeScript
  44. ```
  45. Install [Gulp](https://gulpjs.com/) tools and dev dependencies:
  46. ```bash
  47. npm install -g gulp
  48. npm install
  49. ```
  50. Use one of the following to build and test:
  51. ```
  52. gulp local # Build the compiler into built/local.
  53. gulp clean # Delete the built compiler.
  54. gulp LKG # Replace the last known good with the built one.
  55. # Bootstrapping step to be executed when the built compiler reaches a stable state.
  56. gulp tests # Build the test infrastructure using the built compiler.
  57. gulp runtests # Run tests using the built compiler and test infrastructure.
  58. # Some low-value tests are skipped when not on a CI machine - you can use the
  59. # --skipPercent=0 command to override this behavior and run all tests locally.
  60. # You can override the specific suite runner used or specify a test for this command.
  61. # Use --tests=<testPath> for a specific test and/or --runner=<runnerName> for a specific suite.
  62. # Valid runners include conformance, compiler, fourslash, project, user, and docker
  63. # The user and docker runners are extended test suite runners - the user runner
  64. # works on disk in the tests/cases/user directory, while the docker runner works in containers.
  65. # You'll need to have the docker executable in your system path for the docker runner to work.
  66. gulp runtests-parallel # Like runtests, but split across multiple threads. Uses a number of threads equal to the system
  67. # core count by default. Use --workers=<number> to adjust this.
  68. gulp baseline-accept # This replaces the baseline test results with the results obtained from gulp runtests.
  69. gulp lint # Runs eslint on the TypeScript source.
  70. gulp help # List the above commands.
  71. ```
  72. ## Usage
  73. ```bash
  74. node built/local/tsc.js hello.ts
  75. ```
  76. ## Roadmap
  77. For details on our planned features and future direction please refer to our [roadmap](https://github.com/microsoft/TypeScript/wiki/Roadmap).