blazeofchi/pdf-ocr-rl-qwen3vl2b-sft-grpo
Image-Text-to-Text • Updated • 81
image imagewidth (px) 1.24k 1.24k | markdown stringlengths 200 5.91k | language stringclasses 2
values | source stringclasses 2
values | doc_id stringclasses 757
values | page_num int32 0 51 |
|---|---|---|---|---|---|
# React Compiler Passes Documentation
This directory contains detailed documentation for each pass in the React Compiler pipeline. The compiler transforms React components and hooks to add automatic memoization.
## High-Level Architecture
```
┌─────────────────────────────────────────────────────... | en | en | en_0000_README | 0 | |
│
▼
┌─────────────────────────────────────────────────────────────────────────────────────┐
│ PHASE 3: TYPE & EFFECT INFERENCE │
│ ... | en | en | en_0000_README | 1 | |
▼ │
│ flattenScopesWithHooksOrUseHIR ──▶ propagateScopeDependenciesHIR │
│ │
└────────────────────────────────────────────────────────... | en | en | en_0000_README | 2 | |
pruneUnusedScopes ──▶ mergeReactiveScopesThatInvalidateTogether │
│ │ │
│ ▼ │
│ pruneAlwaysInvalidatingScopes ──▶ propagateEarlyReturn... | en | en | en_0000_README | 3 | |
| # | Pass | File | Description |
|---|------|------|-------------|
| 4 | [constantPropagation](04-constantPropagation.md) | `Optimization/ConstantPropagation.ts` | Sparse conditional constant propagation |
| 5 | [deadCodeElimination](05-deadCodeElimination.md) | `Optimization/DeadCodeElimination.ts` | Remove unreferen... | en | en | en_0000_README | 4 | |
| # | Pass | File | Description |
|---|------|------|-------------|
| 13 | [alignMethodCallScopes](13-alignMethodCallScopes.md) | `ReactiveScopes/AlignMethodCallScopes.ts` | Align method call scopes with receivers |
| 14 | [alignObjectMethodScopes](14-alignObjectMethodScopes.md) | `ReactiveScopes/AlignObjectMethodScope... | en | en | en_0000_README | 5 | |
24 | [pruneNonReactiveDependencies](24-pruneNonReactiveDependencies.md) | `ReactiveScopes/PruneNonReactiveDependencies.ts` | Remove non-reactive dependencies |
| 25 | [pruneUnusedScopes](25-pruneUnusedScopes.md) | `ReactiveScopes/PruneUnusedScopes.ts` | Remove empty scopes |
### Scope Optimization (26-28)
| # | Pass... | en | en | en_0000_README | 6 | |
### Validation (39-55)
| # | Pass | File | Description |
|---|------|------|-------------|
| 39 | [validateContextVariableLValues](39-validateContextVariableLValues.md) | `Validation/ValidateContextVariableLValues.ts` | Variable reference consistency |
| 40 | [validateUseMemo](40-validateUseMemo.md) | `Validation/Vali... | en | en | en_0000_README | 7 | |
51 | [validateExhaustiveDependencies](51-validateExhaustiveDependencies.md) | `Validation/ValidateExhaustiveDependencies.ts` | Dependency array completeness |
| 53 | [validatePreservedManualMemoization](53-validatePreservedManualMemoization.md) | `Validation/ValidatePreservedManualMemoization.ts` | Manual memo preserv... | en | en | en_0000_README | 8 | |
| Flag | Enables Pass |
|------|--------------|
| `enableJsxOutlining` | outlineJSX |
| `enableFunctionOutlining` | outlineFunctions |
| `validateNoSetStateInRender` | validateNoSetStateInRender |
| `enableUseMemoCacheInterop` | Preserves manual memoization |
## Running Tests
```bash
# Run all tests
yarn snap
# Run ... | en | en | en_0000_README | 9 | |
# [React](https://react.dev/) · [](https://github.com/facebook/react/blob/main/LICENSE) [](https://www.npmjs.com/package/react) [ to get a taste of React.
* [Add React to an Existing Project](https://react.dev/learn/add-react-to-an-existing-project) to use as little... | en | en | en_0001_README | 1 | |
const root = createRoot(document.getElementById('container'));
root.render(<HelloMessage name="Taylor" />);
```
This example will render "Hello Taylor" into a container on the page.
You'll notice that we used an HTML-like syntax; [we call it JSX](https://react.dev/learn#writing-markup-with-jsx). JSX is not required t... | en | en | en_0001_README | 2 | |
# React Compiler
React Compiler is a compiler that optimizes React applications, ensuring that only the minimal parts of components and hooks will re-render when state changes. The compiler also validates that components and hooks follow the Rules of React.
More information about the design and architecture of the co... | en | en | en_0002_README | 0 | |
# pruneNonEscapingScopes
## File
`src/ReactiveScopes/PruneNonEscapingScopes.ts`
## Purpose
This pass prunes (removes) reactive scopes whose outputs do not "escape" the component and therefore do not need to be memoized. A value "escapes" in two ways:
1. **Returned from the function** - The value is directly returned... | en | en | en_0003_23-pruneNonEscapingScopes | 0 | |
## Output Guarantees
- **Scopes with non-escaping outputs are removed** - Their instructions are inlined back into the parent scope/function body
- **Scopes with escaping outputs are retained** - Values that escape via return or hook arguments remain memoized
- **Transitive dependencies of escaping scopes are preserved... | en | en | en_0003_23-pruneNonEscapingScopes | 1 | |
### Phase 2: Classify Memoization Levels
Each instruction value is classified:
- `Memoized`: Arrays, objects, function calls, `new` expressions - always potentially aliasing
- `Conditional`: Conditional/logical expressions, property loads - memoized only if dependencies are memoized
- `Unmemoized`: JSX elements (when `... | en | en | en_0003_23-pruneNonEscapingScopes | 2 | |
### Interleaved Mutations
```javascript
const a = [props.a]; // independently memoizable, non-escaping
const b = [];
const c = {};
c.a = a; // c captures a, but c doesn't escape
b.push(props.b); // b escapes via return
return b;
```
Here `a` does not directly escape, but it is a dependency of the sco... | en | en | en_0003_23-pruneNonEscapingScopes | 3 | |
**Input:**
```javascript
function Component(props) {
const a = [props.a];
const b = [];
const c = {};
c.a = a;
b.push(props.b);
return b;
}
```
**Output:**
```javascript
function Component(props) {
const $ = _c(5);
let t0;
if ($[0] !== props.a) {
t0 = [props.a];
$[0] = props.a;
$[1] = t... | en | en | en_0003_23-pruneNonEscapingScopes | 4 | |
# validateNoCapitalizedCalls
## File
`src/Validation/ValidateNoCapitalizedCalls.ts`
## Purpose
This validation pass ensures that capitalized functions are not called directly in a component. In React, capitalized functions are conventionally reserved for components, which should be invoked via JSX syntax rather than ... | en | en | en_0004_42-validateNoCapitalizedCalls | 0 | |
### Rule 2: No Direct Method Calls to Capitalized Properties
Capitalized methods on objects cannot be called directly.
**Error:**
```
Error: Capitalized functions are reserved for components, which must be invoked with JSX. If this is a component, render it with JSX. Otherwise, ensure that it has no hook calls and ren... | en | en | en_0004_42-validateNoCapitalizedCalls | 1 | |
capitalLoadGlobals.set(lvalue.identifier.id, value.binding.name);
}
break;
case 'CallExpression':
// Check if calling a tracked capitalized global
const calleeName = capitalLoadGlobals.get(value.callee.identifier.id);
if (calleeName != null) {
CompilerError.throwInvalid... | en | en | en_0004_42-validateNoCapitalizedCalls | 2 | |
### ALL_CAPS Constants
Functions with names that are entirely uppercase (like `CONSTANTS`) are not flagged:
```javascript
const x = MY_CONSTANT(); // Not an error - all caps indicates a constant, not a component
const y = MyComponent(); // Error - PascalCase indicates a component
```
### Built-in Globals
The default g... | en | en | en_0004_42-validateNoCapitalizedCalls | 3 | |
error.capitalized-function-call.ts:3:12
1 | // @validateNoCapitalizedCalls
2 | function Component() {
> 3 | const x = SomeFunc();
| ^^^^^^^^^^ Capitalized functions are reserved for components...
4 |
5 | return x;
6 | }
```
### Fixture: `error.capitalized-method-call.js`
**Input:**
```ja... | en | en | en_0004_42-validateNoCapitalizedCalls | 4 | |
# Attribute Behavior Fixture
**WIP:** This is an MVP, still needs polish.
### Known Issues
- There are currently two errors thrown when the page loads;
`SyntaxError: missing ; before statement`
## Instructions
`yarn build --type=UMD_DEV react/index,react-dom && cd fixtures/attribute-behavior && yarn install && ya... | en | en | en_0005_README | 0 | |
# DOM Fixtures
A set of DOM test cases for quickly identifying browser issues.
## Setup
To reference a local build of React, first run `yarn build` at the root
of the React project. Then:
```
cd fixtures/dom
yarn
yarn dev
```
The `dev` command runs a script that copies over the local build of react into
the public... | en | en | en_0006_README | 0 | |
# ESLint v10 Fixture
This fixture allows us to test e2e functionality for `eslint-plugin-react-hooks` with eslint version 10.
Run the following to test.
```sh
cd fixtures/eslint-v10
yarn
yarn build
yarn lint
```
| en | en | en_0007_README | 0 | |
# ESLint v6 Fixture
This fixture allows us to test e2e functionality for `eslint-plugin-react-hooks` with eslint version 6.
Run the following to test.
```sh
cd fixtures/eslint-v6
yarn
yarn build
yarn lint
```
| en | en | en_0008_README | 0 | |
# ESLint v7 Fixture
This fixture allows us to test e2e functionality for `eslint-plugin-react-hooks` with eslint version 7.
Run the following to test.
```sh
cd fixtures/eslint-v7
yarn
yarn build
yarn lint
```
| en | en | en_0009_README | 0 | |
# ESLint v8 Fixture
This fixture allows us to test e2e functionality for `eslint-plugin-react-hooks` with eslint version 8.
Run the following to test.
```sh
cd fixtures/eslint-v8
yarn
yarn build
yarn lint
```
| en | en | en_0010_README | 0 | |
# ESLint v9 Fixture
This fixture allows us to test e2e functionality for `eslint-plugin-react-hooks` with eslint version 9.
Run the following to test.
```sh
cd fixtures/eslint-v9
yarn
yarn build
yarn lint
```
| en | en | en_0011_README | 0 | |
# Fiber Debugger
This is a debugger handy for visualizing how [Fiber](https://github.com/facebook/react/issues/6170) works internally.
**It is only meant to be used by React contributors, and not by React users.**
It is likely that it might get broken at some point. If it's broken, ping [Dan](https://twitter.com/dan... | en | en | en_0012_README | 0 | |
# Fizz Fixtures
A set of basic tests for Fizz primarily focused on baseline performance of legacy renderToString and streaming implementations.
## Setup
To reference a local build of React, first run `npm run build` at the root
of the React project. Then:
```
cd fixtures/fizz
yarn
yarn start
```
The `start` comman... | en | en | en_0013_README | 0 | |
# Legacy JSX Runtimes
This is an internal testing fixture for the special JSX runtime versions released for 0.14, 15, and 16.
They are checked into the corresponding `react-*/cjs/*` folders.
Run the full regression suite:
```
yarn
yarn test
```
| en | en | en_0014_README | 0 | |
# Nested React Demo
This is a demo of how you can configure a build system to serve **two different versions of React** side by side in the same app. This is not optimal, and should only be used as a compromise to prevent your app from getting stuck on an old version of React.
## You Probably Don't Need This
Note th... | en | en | en_0015_README | 0 | |
This demo uses two different versions of React: React 17 for "modern" components (in `src/modern`), and React 16.8 for "legacy" components (in `src/legacy`).
**We still recommend upgrading your whole app to React 17 in one piece.** The React 17 release intentionally has minimal breaking changes so that it's easier to ... | en | en | en_0015_README | 1 | |
- How to install two versions of React in a single app with npm side by side.
- How to avoid the ["invalid Hook call" error](https://github.com/facebook/react/issues/13991) while nesting React trees.
- How to pass context between different versions of React.
- How to lazy-load the second React bundle so it's only loade... | en | en | en_0015_README | 2 | |
**`src/modern/package.json`**: This is where we declare the `react` and `react-dom` dependencies for the "modern" trees. In this demo, we're using React 17. Here, we also specify third-party dependencies that use React and are used from the modern part of our app. This is why we *also* have `react-router` and `react-... | en | en | en_0015_README | 3 | |
Loading two Reacts on the same page is bad for the user experience, so you should strive to push this as far as possible from the critical path of your app. For example, if there is a dialog that is less commonly used, or a route that is rarely visited, those are better candidates for staying on an older version of Rea... | en | en | en_0015_README | 4 | |
If you have nested trees managed by different versions of React, the inner tree won't "see" the outer tree's Context.
This breaks third-party libraries like React Redux or React Router, as well as any of your own usage of Context (for example, for theming).
To solve this problem, we read all the Contexts we care abou... | en | en | en_0015_README | 5 | |
ent listener at the `document` level. React 17 fixes this by attaching handlers to the roots. We strongly recommend upgrading to React 17 before considering the nesting strategy for future upgrades.
### Gotchas
This setup is unusual, so it has a few gotchas.
* Don't add `package.json` to the `src/shared` folder. For... | en | en | en_0015_README | 6 | |
# Getting Started with Create React App
This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app).
## Available Scripts
In the project directory, you can run:
### `yarn start`
Runs the app in the development mode.\
Open [http://localhost:3000](http://localhost:3000) to vie... | en | en | en_0016_README | 0 | |
You don't have to ever use `eject`. The curated feature set is suitable for small and middle deployments, and you shouldn't feel obligated to use this feature. However we understand that this tool wouldn't be useful if you couldn't customize it when you are ready for it.
## Learn More
You can learn more in the [Creat... | en | en | en_0016_README | 1 | |
# Manual Testing Fixtures
This folder exists for **React contributors** only.
If you use React, you don't need to worry about it.
These fixtures verify that the built React distributions are usable in different environments.
**They are not running automatically.** (At least not yet. Feel free to contribute to aut... | en | en | en_0017_README | 0 | |
# SSR Fixtures
A set of test cases for quickly identifying issues with server-side rendering.
## Setup
To reference a local build of React, first run `npm run build` at the root
of the React project. Then:
```
cd fixtures/ssr
yarn
yarn start
```
The `start` command runs a webpack dev server and a server-side rende... | en | en | en_0018_README | 0 | |
# SSR Fixtures
A set of test cases for quickly identifying issues with server-side rendering.
## Setup
To reference a local build of React, first run `npm run build` at the root
of the React project. Then:
```
cd fixtures/ssr2
yarn
yarn start
```
The `start` command runs a webpack dev server and a server-side rend... | en | en | en_0019_README | 0 | |
# View Transition
A test case for View Transitions.
## Setup
To reference a local build of React, first run `npm run build` at the root
of the React project. Then:
```
cd fixtures/view-transition
yarn
yarn start
```
The `start` command runs a webpack dev server and a server-side rendering server in development mod... | en | en | en_0020_README | 0 | |
# `dom-event-testing-library`
A library for unit testing events via high-level interactions, e.g., `pointerdown`,
that produce realistic and complete DOM event sequences.
There are number of challenges involved in unit testing modules that work with
DOM events.
1. Gesture recognizers may need to support environments... | en | en | en_0021_README | 0 | |
// test all the pointer types supported by the environment
testWithPointerType('pointer down', pointerType => {
const ref = createRef(null);
const onTapStart = jest.fn();
render(() => {
useTap(ref, { onTapStart });
return <div ref={ref} />
});
// create an event target
const tar... | en | en | en_0021_README | 1 | |
# `eslint-plugin-react-hooks`
The official ESLint plugin for [React](https://react.dev) which enforces the [Rules of React](https://react.dev/reference/eslint-plugin-react-hooks) and other best practices.
## Installation
Assuming you already have ESLint installed, run:
```sh
# npm
npm install eslint-plugin-react-ho... | en | en | en_0022_README | 0 | |
```js
{
"extends": ["plugin:react-hooks/recommended"],
// ...
}
```
### Custom Configuration
If you want more fine-grained configuration, you can instead choose to enable specific rules. However, we strongly encourage using the recommended presets — see above — so that you will automatically receive new recommen... | en | en | en_0022_README | 1 | |
'react-hooks/refs': 'error',
'react-hooks/set-state-in-effect': 'error',
'react-hooks/set-state-in-render': 'error',
'react-hooks/static-components': 'error',
'react-hooks/unsupported-syntax': 'warn',
'react-hooks/use-memo': 'error',
'react-hooks/incompatible-library': 'warn',
... | en | en | en_0022_README | 2 | |
"react-hooks/static-components": "error",
"react-hooks/unsupported-syntax": "warn",
"react-hooks/use-memo": "error",
"react-hooks/incompatible-library": "warn"
}
}
```
## Advanced Configuration
`exhaustive-deps` can be configured to validate dependencies of custom Hooks with the `additionalHooks` opt... | en | en | en_0022_README | 3 | |
# React ART
React ART is a JavaScript library for drawing vector graphics using [React](https://github.com/facebook/react/).
It provides declarative and reactive bindings to the [ART library](https://github.com/sebmarkbage/art/).
Using the same declarative API you can render the output to either Canvas, SVG or VML (... | en | en | en_0023_README | 0 | |
# react-cache
A basic cache for React applications. It also serves as a reference for more
advanced caching implementations.
This package is meant to be used alongside yet-to-be-released, experimental
React features. It's unlikely to be useful in any other context.
**Do not use in a real application.** We're publish... | en | en | en_0024_README | 0 | |
# react-client
This is an experimental package for consuming custom React streaming models.
**Its API is not as stable as that of React, React Native, or React DOM, and does not follow the common versioning scheme.**
**Use it at your own risk.**
| en | en | en_0025_README | 0 | |
# react-debug-tools
This is an experimental package for debugging React renderers.
**Its API is not as stable as that of React, React Native, or React DOM, and does not follow the common versioning scheme.**
**Use it at your own risk.**
| en | en | en_0026_README | 0 | |
# `react-devtools-core`
This package provides low-level APIs to support renderers like [React Native](https://github.com/facebook/react-native). If you're looking for the standalone React DevTools UI, **we suggest using [`react-devtools`](https://github.com/facebook/react/tree/main/packages/react-devtools) instead of ... | en | en | en_0027_README | 0 | |
`shouldStartProfilingNow` | Optional. Whether to start profiling immediately after installing the hook. Defaults to `false`. |
| `profilingSettings` | Optional. Profiling settings used when `shouldStartProfilingNow` is `true`. Defaults to `{ recordChangeDescriptions: false, recordTimeline: false }`. |
| `compone... | en | en | en_0027_README | 1 | |
breakOnConsoleErrors: false,<br> showInlineWarningsAndErrors: true,<br> hideConsoleLogsInStrictMode: false,<br> disableSecondConsoleLogDimmingInStrictMode: false<br>}</pre> |
#### Component filters
Each filter object must include `type` and `isEnabled`. Some filters also require `value` or `isValid`.
| Type | Requ... | en | en | en_0027_README | 2 | |
`host` | `"localhost"` | Socket connection to frontend should use this host. |
| `isAppActive` | | (Optional) function that returns true/false, telling DevTools when it's ready to connect to React. ... | en | en | en_0027_README | 3 | |
`onSettingsUpdated` | | A callback that will be called when the user updates the settings in the UI. You can use it for persisting user settings. | |
### `connectWithCustomMessagingProtocol` options
| Prop ... | en | en | en_0027_README | 4 | |
### Example
```js
import DevtoolsUI from "react-devtools-core/standalone";
// See the full list of API methods in documentation below.
const { setContentDOMNode, startServer } = DevtoolsUI;
// Render DevTools UI into a DOM element.
setContentDOMNode(document.getElementById("container"));
// Start socket server used ... | en | en | en_0027_README | 5 | |
#### `setProjectRoots(roots: Array<string>)`
_Optional_ set of root directories for source files. These roots can be used to open an inspected component's source code using an IDE.
#### `setStatusListener(callback: Function)`
_Optional_ callback to be notified of socket server events (e.g. initialized, errored, connec... | en | en | en_0027_README | 6 | |
When connecting through a reverse proxy, the client may need to connect to a different host, port, or protocol than the local server. Use `clientOptions` to override what appears in the `connectToDevTools()` script served to clients. Any field not set falls back to the corresponding server value.
| Field | Default | D... | en | en | en_0027_README | 7 | |
# TypeScript
[](https://github.com/microsoft/TypeScript/actions/workflows/ci.yml)
[](https://www.npmjs.com/package/typescript)
[ to TypeScript.
* [Submit bugs](https://github.com/microsoft/TypeScript/issues) and help us verify fixes as they are checked in.
* Review the [source code changes](https://github.com/microsoft/TypeScript/pulls).
* Enga... | en | en | en_0028_README | 1 | |
# Read this!
The files within this directory are copied and deployed with TypeScript as the set of APIs available as a part of the JavaScript language.
There are three main domains of APIs in `src/lib`:
- **ECMAScript language features** - e.g. JavaScript APIs like functions on Array etc which are documented in [... | en | en | en_0029_README | 0 | |
# How does TypeScript formatting work?
To format code you need to have a formatting context and a `SourceFile`. The formatting context contains
all user settings like tab size, newline character, etc.
The end result of formatting is represented by TextChange objects which hold the new string content, and
the text ... | en | en | en_0030_README | 0 | |
As it recurses, `processNode` is called on the children setting the indentation is decided and passed
through into each of that node's children.
The meat of formatting decisions is made via `processPair`, the pair here being the current node and the previous node. `processPair` which mutates the formatting context to... | en | en | en_0030_README | 1 | |
// === Auto Imports ===
```ts
// @Filename: /main.ts
/*|*/
```
## From completions
- `Component` from `"./Component"`
- `fromAtTypesFoo` from `"foo"`
- `fromBar` from `"bar"`
- `fromLocal` from `"./local"`
```ts
import { Component } from "./Component";
Component
```
```ts
import { fromAtTypesFoo } from "foo";
fro... | en | en | en_0031_autoImportAllowTsExtensions1.baseline | 0 | |
// === Auto Imports ===
```ts
// @Filename: /main.ts
/*|*/
```
## From completions
- `Component` from `"./Component.tsx"`
- `fromAtTypesFoo` from `"foo"`
- `fromBar` from `"bar"`
- `fromLocal` from `"./local.ts"`
```ts
import { Component } from "./Component.tsx";
Component
```
```ts
import { fromAtTypesFoo } from ... | en | en | en_0032_autoImportAllowTsExtensions2.baseline | 0 | |
// === Auto Imports ===
```ts
// @Filename: /main.ts
import { Component } from "./Component.tsx";
/*|*/
```
## From completions
- `fromDecl` from `"./decl"`
- `fromLocal` from `"./local.ts"`
```ts
import { Component } from "./Component.tsx";
import { fromDecl } from "./decl";
fromDecl
```
```ts
import { Component }... | en | en | en_0033_autoImportAllowTsExtensions3.baseline | 0 | |
// === Auto Imports ===
```ts
// @Filename: /main.ts
import { Component } from "./local.js";
/*|*/
```
## From completions
- `fromDecl` from `"./decl.js"`
- `fromLocal` from `"./local.js"`
```ts
import { fromDecl } from "./decl.js";
import { Component } from "./local.js";
fromDecl
```
```ts
import { Component, from... | en | en | en_0034_autoImportAllowTsExtensions4.baseline | 0 | |
// === Auto Imports ===
```ts
// @Filename: /a.ts
/*|*/
```
## From completions
- `coolName` from `"./cool-name"`
- `explode` from `"./cool-name"`
- `isAbsolute` from `"path"`
- `join` from `"path"`
- `normalize` from `"path"`
- `path` from `"path"`
- `resolve` from `"path"`
```ts
import coolName = require("./cool-n... | en | en | en_0035_autoImportVerbatimCJS1.baseline | 0 | |
## From codefixes
### When marker text is `normalize`
Add import from "path"
```ts
import path = require("path");
path.normalize
```
### When marker text is `join`
Add import from "path"
```ts
import path = require("path");
path.join
```
### When marker text is `path`
Add import from "path"
```ts
import path... | en | en | en_0035_autoImportVerbatimCJS1.baseline | 1 | |
# Note
🚨 **Important** 🚨: All code changes should be submitted to the https://github.com/microsoft/typescript-go repo. Development in this codebase [is winding down](https://devblogs.microsoft.com/typescript/progress-on-typescript-7-december-2025/#typescript-6.0-is-the-last-javascript-based-release) and PRs will onl... | en | en | en_0036_CONTRIBUTING | 0 | |
* If you have a crash, search for the first few topmost function names shown in the call stack.
## 3. Do you have a question?
The issue tracker is for **issues**, in other words, bugs and suggestions.
If you have a *question*, please use [Stack Overflow](https://stackoverflow.com/questions/tagged/typescript), [Gitter... | en | en | en_0036_CONTRIBUTING | 1 | |
# Instructions for Contributing Code (Legacy)
## What You'll Need
0. [A bug or feature you want to work on](https://github.com/microsoft/TypeScript/issues?q=is%3Aissue%20label%3A%22Help%20Wanted%22)!
1. [A GitHub account](https://github.com/join).
2. A copy of the TypeScript code. See the next steps for instructions.... | en | en | en_0036_CONTRIBUTING | 2 | |
```
hereby local # Build the compiler into built/local.
hereby clean # Delete the built compiler.
hereby LKG # Replace the last known good with the built one.
# Bootstrapping step to be executed when the built compiler reaches a stable state.
hereby tests ... | en | en | en_0036_CONTRIBUTING | 3 | |
- Clone the TypeScript repository locally and use the `Open Folder in Container` command.
- Use the `Clone Repository in Container Volume` command to clone the TypeScript repository into a new container.
### Faster clones
The TypeScript repository is relatively large. To save some time, you might want to clone it wit... | en | en | en_0036_CONTRIBUTING | 4 | |
Features (things that add new or improved functionality to TypeScript) may be accepted, but will need to first be approved (labelled ["help wanted"](https://github.com/Microsoft/TypeScript/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) or in the "Backlog" milestone) by a TypeScript project maintainer in the s... | en | en | en_0036_CONTRIBUTING | 5 | |
Your pull request should:
* Include a description of what your change intends to do
* Be based on reasonably recent commit in the **main** branch
* Include adequate tests
* At least one test should fail in the absence of your non-test code changes. If your PR does not match this criteria, please specify why
* ... | en | en | en_0036_CONTRIBUTING | 6 | |
Any changes should be made to [src/lib](https://github.com/Microsoft/TypeScript/tree/main/src/lib). **Most** of these files can be updated by hand, with the exception of any generated files (see below).
Library files in `built/local/` are updated automatically by running the standard build task:
```sh
hereby
```
The... | en | en | en_0036_CONTRIBUTING | 7 | |
You can debug with VS Code or Node instead with `hereby runtests -i`:
```Shell
hereby runtests --tests=2dArrays -i
```
You can also use the [provided VS Code launch configuration](./.vscode/launch.template.json) to launch a debug session for an open test file. Rename the file 'launch.json', open the test file of inte... | en | en | en_0036_CONTRIBUTING | 8 | |
- the `.js` and `.d.ts` output (all in the same `.js` output file),
- the errors produced by the compiler (in an `.errors.txt` file),
- the types of each expression (in a `.types` file),
- the symbols for each identifier (in a `.symbols` file), and
- the source map outputs for files if a test opts into them (in a `.js.... | en | en | en_0036_CONTRIBUTING | 9 | |
# canWatchAffectingLocation
Determines if package.json that was found during module resolution and change in it will affect resolution can be watched.
## Testing for Dos root: c:/
| File | canWatchAffectingLocation |
| -------------------... | en | en | en_0037_canWatchAffectingLocationDos.baseline | 0 | |
c:/users/username/folderAtRoot/folder1/folder2/folder3/folder4/package.json | true |
| c:/users/username/folderAtRoot/folder1/folder2/folder3/folder4/folder5/package.json | true |
| c:/user/package.json | t... | en | en | en_0037_canWatchAffectingLocationDos.baseline | 1 | |
c:/usr/username/folderAtRoot/folder1/folder2/folder3/folder4/folder5/package.json | true |
| c:/home/package.json | true |
| c:/home/username/package.json | t... | en | en | en_0037_canWatchAffectingLocationDos.baseline | 2 | |
# canWatchAffectingLocation
Determines if package.json that was found during module resolution and change in it will affect resolution can be watched.
## Testing for Posix root: /
| File | canWatchAffectingLocation |
| ---------------------... | en | en | en_0038_canWatchAffectingLocationPosix.baseline | 0 | |
/users/username/folderAtRoot/folder1/folder2/folder3/folder4/package.json | true |
| /users/username/folderAtRoot/folder1/folder2/folder3/folder4/folder5/package.json | true |
| /user/package.json | false ... | en | en | en_0038_canWatchAffectingLocationPosix.baseline | 1 | |
/usr/username/folderAtRoot/folder1/folder2/folder3/folder4/folder5/package.json | true |
| /home/package.json | false |
| /home/username/package.json | false ... | en | en | en_0038_canWatchAffectingLocationPosix.baseline | 2 | |
# canWatchAffectingLocation
Determines if package.json that was found during module resolution and change in it will affect resolution can be watched.
## Testing for Unc root: //vda1cs4850/
| File | canWatchAffectingLocation |
|... | en | en | en_0039_canWatchAffectingLocationUnc.baseline | 0 | |
//vda1cs4850/users/username/folderAtRoot/package.json | true |
| //vda1cs4850/users/username/folderAtRoot/folder1/package.json | true |
| //vda1cs4850/users/username/folderAtRoot/folder1/folder2/package.js... | en | en | en_0039_canWatchAffectingLocationUnc.baseline | 1 | |
//vda1cs4850/user/username/folderAtRoot/folder1/folder2/folder3/folder4/folder5/package.json | true |
| //vda1cs4850/usr/package.json | false |
| //vda1cs4850/usr/username/package.json ... | en | en | en_0039_canWatchAffectingLocationUnc.baseline | 2 | |
//vda1cs4850/home/username/folderAtRoot/folder1/package.json | true |
| //vda1cs4850/home/username/folderAtRoot/folder1/folder2/package.json | true |
| //vda1cs4850/home/username/folderAtRoot/folder1/folder2/folder3/pac... | en | en | en_0039_canWatchAffectingLocationUnc.baseline | 3 | |
# canWatchAffectingLocation
Determines if package.json that was found during module resolution and change in it will affect resolution can be watched.
## Testing for UncDos root: //vda1cs4850/c$
| File | canWatchAffectingLoca... | en | en | en_0040_canWatchAffectingLocationUncDos.baseline | 0 | |
//vda1cs4850/c$/users/username/folderAtRoot/package.json | true |
| //vda1cs4850/c$/users/username/folderAtRoot/folder1/package.json | true |
| //vda1cs4850/c$/users/username/folderAtRoot/folder1/folder2/p... | en | en | en_0040_canWatchAffectingLocationUncDos.baseline | 1 | |
//vda1cs4850/c$/user/username/folderAtRoot/folder1/folder2/folder3/folder4/folder5/package.json | true |
| //vda1cs4850/c$/usr/package.json | true |
| //vda1cs4850/c$/usr/username/package.json ... | en | en | en_0040_canWatchAffectingLocationUncDos.baseline | 2 | |
//vda1cs4850/c$/home/username/folderAtRoot/folder1/package.json | true |
| //vda1cs4850/c$/home/username/folderAtRoot/folder1/folder2/package.json | true |
| //vda1cs4850/c$/home/username/folderAtRoot/folder1/folder2/fo... | en | en | en_0040_canWatchAffectingLocationUncDos.baseline | 3 |
End of preview. Expand in Data Studio
README.md exists but content is empty.
- Downloads last month
- 23