# Third-party notices

JS with Types (jswithtypes.com) quotes a small amount of text from other projects. The site's own text, design
and code examples are not covered by these notices; see the terms page for those.

## TypeScript

- Project: TypeScript, https://github.com/microsoft/TypeScript
- Copyright: Microsoft Corporation
- License: Apache License, Version 2.0, https://www.apache.org/licenses/LICENSE-2.0

What the site quotes, word for word and marked as quoted where it appears:

- the one-line description of each compiler option on the config pages (`/config/<option>/`), as TypeScript
  prints it in `tsc --help` and ships it in its option table; every build checks each quote against
  the installed TypeScript;
- the diagnostic messages shown under failing examples, which are the messages `tsc` reports (TypeScript's
  `diagnosticMessages.json`);
- on each error page (`/errors/ts<code>/`), the message template for the page's code and for the companion codes
  the page also explains (for example TS2363 on the TS2362 page), with their `{0}`-style placeholders, quoted from
  `diagnosticMessages.json` for TypeScript 5.9.3; every build checks each template against the installed
  TypeScript.

The same quotations appear in the data files published under `/data/` (`config-options.json`:
`officialDescription`; `diagnostics.json`: `message` and the messages in `alsoCovers`), where they keep this license;
the site's own text in those files is published under CC BY 4.0 (see `/data/`).

The TypeScript release pages (`/typescript/<version>/`) describe each release in the site's own words and link to its
release notes and announcement; they quote no sentences from them. Error codes named there for TypeScript 6.0 and 7.0
come from one-off runs of those versions, not from quoted text.

No TypeScript source code is copied into the site. The site's build runs TypeScript (an npm development
dependency) to check every example.

## SchemaStore tsconfig.json schema

- Project: SchemaStore, https://github.com/SchemaStore/schemastore (the schema is served at
  https://json.schemastore.org/tsconfig.json)
- License: Apache License, Version 2.0, https://www.apache.org/licenses/LICENSE-2.0

What the site quotes: one sentence from the description of each of four top-level `tsconfig.json` keys (`include`,
`exclude`, `files`, `extends`), which TypeScript itself ships without a description. Each is marked as quoted
from this schema on its page, and the same sentences appear as `officialDescription` in `/data/config-options.json`.

## Short quotations and printed output (wave 4b)

- The guide on reading error messages (`/guides/read-a-typescript-error-message/`) shows the output `tsc` 5.9.3 printed for
  two of the site's own examples, in its plain and `--pretty` forms (colors removed). That output consists of
  TypeScript's diagnostic messages (above) and the site's own code; the line numbers are changed to match the example
  as the page shows it, without its hidden marker lines.
- The guide listing projects that check JavaScript with JSDoc (`/guides/who-checks-javascript-with-jsdoc/`) quotes one
  phrase of ten words from a public comment by a Svelte maintainer, attributed and linked. Every other project's stated
  reason is described in the site's own words, with a link to the source.
- The types finder (`/tools/types-finder/`) shows data the npm registry returns at the moment of the lookup (names,
  versions, licenses, deprecation notices); none of it is stored in the site. The tests keep a few trimmed registry
  manifests as fixtures (`tests/fixtures/registry/`), which are not published on the site.

## Changes

The quoted descriptions are reproduced unchanged. They appear in a table cell marked as TypeScript's (or the
schema's) description, next to the site's own explanation.

The diagnostic message templates on the error pages are reproduced unchanged. In the messages printed under
examples, one change is made: where TypeScript names a file by its absolute path on the machine that ran the
check, the path is shown as it would be for a project at `/project` (for example
`/project/node_modules/legacy-slugify/index.js`). The rest of each message is TypeScript's text.