tsifdef 1.1.8

package/CHANGELOG.md

@@ -0,0 +1,25 @@
+# Changelog
+
+## v1.1.8 - 2026-09-11
+
+First public release.
+
+- `#if` / `#elif` / `#else` / `#endif` conditional compilation for TypeScript,
+  driven by a Profile: a JSON array of enabled macro names referenced from
+  `package.json`.
+- `tsifdef build` compiles through TypeScript with inactive branches masked at
+  equal length, so emitted `.js`, `.js.map` sources, `.d.ts`, and error paths
+  point at the original files. Incremental builds and `--watch` are supported.
+- VSCode extension that dims and folds inactive branches and shows the active
+  Profile in the status bar.
+- tsserver plugin, shipped in the same VSIX, so the language service reports no
+  errors on inactive code and treats unknown macros as `false`.
+- ESLint processor and parser wrapper in the same npm package. Diagnostics keep
+  their real line and column, autofix and quick fixes keep working, and
+  formatting rules such as `prettier/prettier` can stay enabled.
+- Flat config via `tsifdef.configs["flat/recommended"]`, and legacy `.eslintrc`
+  via `extends: ["plugin:tsifdef/recommended"]`.
+- Supports ESLint 8.57 and 9 with `@typescript-eslint/parser` 5 through 8, both
+  as optional peer dependencies.
+- Portable specification and implementation-neutral conformance fixtures under
+  `spec/`.

package/CHANGELOG.zh-CN.md

@@ -0,0 +1,22 @@
+# 更新日志
+
+## v1.1.8 - 2026-09-11
+
+首个公开版本。
+
+- 为 TypeScript 提供 `#if` / `#elif` / `#else` / `#endif` 条件编译，由 Profile
+  驱动：一个列出已启用宏名的 JSON 数组，通过 `package.json` 引用。
+- `tsifdef build` 以等长遮盖未激活分支的方式交给 TypeScript 编译，因此产出的
+  `.js`、`.js.map` sources、`.d.ts` 和报错路径都指向原始文件。支持增量编译和
+  `--watch`。
+- VSCode 扩展：置灰并折叠未激活分支，在状态栏显示当前 Profile。
+- tsserver 插件随同一个 VSIX 发布，语言服务不再对未激活代码报错，未知宏按
+  `false` 处理。
+- ESLint processor 和 parser wrapper 包含在同一个 npm 包中。诊断保留真实行列
+  位置，自动修复和快速修复正常工作，`prettier/prettier` 等格式化规则可以保持
+  开启。
+- Flat Config 使用 `tsifdef.configs["flat/recommended"]`；旧版 `.eslintrc` 使用
+  `extends: ["plugin:tsifdef/recommended"]`。
+- 支持 ESLint 8.57 和 9，以及 `@typescript-eslint/parser` 5 至 8，两者均为
+  optional peer dependency。
+- `spec/` 下提供可移植规范和与实现无关的一致性用例。

package/CONTRIBUTING.md

@@ -0,0 +1,52 @@
+# Contributing to TSIfDef
+
+Thank you for helping improve TSIfDef.
+
+## Development setup
+
+Requirements:
+
+- Node.js 18.17 or newer
+- npm
+- VSCode 1.85 or newer for extension changes
+
+Install dependencies and build the project:
+
+```bash
+npm install
+npm run build
+```
+
+## Making changes
+
+- Keep changes focused on one problem.
+- Add or update tests when behavior changes.
+- Use English for code comments and public API documentation.
+- Do not commit generated `dist/`, `.test-dist/`, `release/`, or `node_modules/` files.
+- Update `CHANGELOG.md` for user-visible changes.
+
+Run the full test suite before opening a pull request:
+
+```bash
+npm test
+```
+
+Pull requests must pass the `Test` and `Build` workflows. Maintainers publish
+versioned artifacts through the manually triggered `Release` workflow.
+
+Maintainers can verify release artifacts with:
+
+```bash
+npm run release
+```
+
+This command builds, packages, installs, and smoke-tests both the npm tarball and
+the VSIX.
+
+## Pull requests
+
+Describe the problem, the chosen solution, and any compatibility impact. Keep
+commits reviewable and avoid unrelated formatting changes.
+
+Report security issues through the process in [`SECURITY.md`](./SECURITY.md),
+not through a public issue.

package/INTEGRATION.md

@@ -0,0 +1,166 @@
+# Integrating TSIfDef into a Project
+
+Language file: [`INTEGRATION.zh-CN.md`](./INTEGRATION.zh-CN.md)
+
+How to adopt TSIfDef in a TypeScript project: build, editor, and lint. The three
+are independent — adopt only the pieces you need. All three read the same
+Profile.
+
+## 1. Concepts
+
+- A **macro** is a plain identifier such as `BROWSER` or `EXPERIMENTAL`.
+- A **Profile** is a JSON array of the enabled macro names. Any name not listed
+  evaluates to `false`; unknown names are not an error.
+- `package.json` holds the single pointer to the active Profile via the
+  `tsifdef` field. Build, VSCode, tsserver, and ESLint all read it.
+
+```jsonc
+// package.json
+{
+  "tsifdef": "./Profiles/browser.json",
+  "scripts": {
+    "compile": "tsifdef build"
+  }
+}
+```
+
+```jsonc
+// Profiles/browser.json
+["BROWSER", "EXPERIMENTAL"]
+```
+
+How the Profile is produced — by hand, by a script, or by another toolchain — is
+up to your project. If it is generated, keep it out of source control and make
+the build fail when it is missing: a stale Profile silently produces wrong
+output.
+
+## 2. Build
+
+Install the package and compile with `tsifdef build` instead of `tsc`:
+
+```bash
+npm install -D tsifdef
+```
+
+```jsonc
+"scripts": {
+  "compile": "tsifdef build",
+  "watch": "tsifdef build --watch"
+}
+```
+
+Emitted `.js.map` sources, `.d.ts`, and error paths all point at your original
+files, so nothing downstream needs to know TSIfDef ran.
+
+```bash
+tsifdef build -p ./custom.tsconfig.json
+tsifdef build -p ./tsconfig.json -- --module commonjs --outDir dist
+```
+
+`-p`/`--project` selects a tsconfig; arguments after `--` are tsc options that
+override it. Switching Profiles triggers a full rebuild automatically.
+`outFile` and composite references (`tsc -b`) are not supported.
+
+## 3. Editor (VSCode)
+
+Two pieces make `#if` gray out and stop erroring:
+
+1. **VSCode extension** — install the TSIfDef VSIX. It grays out and folds
+   inactive branches and shows the active Profile in the status bar.
+2. **tsserver plugin** — ships inside that VSIX and makes the language service
+   ignore inactive code. It loads through the workspace TypeScript version, so
+   point the workspace at its local TypeScript:
+
+```jsonc
+// .vscode/settings.json  (or the *.code-workspace settings)
+{
+  "typescript.tsdk": "node_modules/typescript/lib",
+  "typescript.enablePromptUseWorkspaceTsdk": true
+}
+```
+
+Then run `TypeScript: Restart TS Server`. Inactive code no longer errors, and
+`#if UNKNOWN_MACRO` is treated as `false` rather than "unknown macro".
+
+Run `TypeScript: Restart TS Server` after upgrading the extension too — the
+running server keeps the old plugin until it restarts.
+
+## 4. ESLint
+
+Without TSIfDef, raw `#if` lines are reported as parse errors. The ESLint
+processor is already in the `tsifdef` package installed for the build; no second
+package is required.
+
+Add the recommended config after the project's existing TypeScript flat config:
+
+```javascript
+// eslint.config.mjs
+import tsParser from "@typescript-eslint/parser";
+import tsifdef from "tsifdef/eslint-plugin";
+
+export default [
+  {
+    files: ["**/*.{ts,tsx,mts,cts}"],
+    languageOptions: { parser: tsParser },
+  },
+  tsifdef.configs["flat/recommended"],
+];
+```
+
+Keep the project's normal `@typescript-eslint/parser` as the top-level parser so
+editor integrations still recognize TypeScript validation.
+
+No rules need to be turned off. Diagnostics report at their real line and
+column, autofix and editor quick fixes work, and formatting rules such as
+`prettier/prettier` stay enabled: inactive branches never produce formatting
+complaints, while real issues in active code are still reported normally. The
+only thing TSIfDef withholds is a fix that would overwrite a `#if` line — that
+diagnostic is still reported, just without the automatic repair.
+
+TSIfDef supports ESLint 8.57 and 9 with `@typescript-eslint/parser` 5 through 8.
+Both are optional peer dependencies, so the host project controls their versions.
+
+### Legacy `.eslintrc`
+
+The legacy config system resolves `tsifdef` as a package named
+`eslint-plugin-tsifdef`, so install the same package under that alias:
+
+```bash
+npm install -D eslint-plugin-tsifdef@npm:tsifdef
+# or, for an offline release artifact:
+npm install -D eslint-plugin-tsifdef@file:./tsifdef-<version>.tgz
+```
+
+```jsonc
+// .eslintrc.json
+{
+  "parser": "@typescript-eslint/parser",
+  "extends": ["plugin:tsifdef/recommended"]
+}
+```
+
+That sets the plugin, the processor, and the `import/parsers` setting. Put it
+**last** in `extends` if the project also extends `plugin:import/typescript`:
+that config registers `@typescript-eslint/parser` for the same extensions, and
+`eslint-plugin-import` uses whichever parser is listed first.
+
+To wire the pieces up by hand instead:
+
+```jsonc
+// .eslintrc.json
+{
+  "parser": "@typescript-eslint/parser",
+  "plugins": ["tsifdef"],
+  "overrides": [
+    {
+      "files": ["*.ts", "*.mts", "*.cts", "*.tsx"],
+      "processor": "tsifdef/macros"
+    }
+  ],
+  "settings": {
+    "import/parsers": {
+      "eslint-plugin-tsifdef/parser": [".ts", ".tsx", ".mts", ".cts"]
+    }
+  }
+}
+```

package/INTEGRATION.zh-CN.md

@@ -0,0 +1,159 @@
+# 在项目中集成 TSIfDef
+
+Language file: [`INTEGRATION.md`](./INTEGRATION.md)
+
+如何在 TypeScript 项目里接入 TSIfDef：构建、编辑器、lint。三者相互独立，按需采用
+其中任意部分即可。它们读同一个 Profile。
+
+## 1. 概念
+
+- **宏**是一个普通标识符，例如 `BROWSER` 或 `EXPERIMENTAL`。
+- **Profile** 是一个 JSON 数组，列出已启用的宏名。未列出的名字求值为 `false`；
+  未知名字不报错。
+- `package.json` 通过 `tsifdef` 字段持有指向当前 Profile 的唯一指针。构建、
+  VSCode、tsserver 和 ESLint 都从它读取。
+
+```jsonc
+// package.json
+{
+  "tsifdef": "./Profiles/browser.json",
+  "scripts": {
+    "compile": "tsifdef build"
+  }
+}
+```
+
+```jsonc
+// Profiles/browser.json
+["BROWSER", "EXPERIMENTAL"]
+```
+
+Profile 如何产生——手写、脚本生成，或由另一套工具链生成——由你的项目决定。如果
+它是生成物，请不要纳入源码控制，并让构建在文件缺失时失败：过期的 Profile 会静默
+产出错误输出。
+
+## 2. 构建
+
+安装包，用 `tsifdef build` 代替 `tsc` 编译：
+
+```bash
+npm install -D tsifdef
+```
+
+```jsonc
+"scripts": {
+  "compile": "tsifdef build",
+  "watch": "tsifdef build --watch"
+}
+```
+
+emit 出的 `.js.map` sources、`.d.ts` 和报错路径都指向你的原始文件，因此下游工具
+无需知道 TSIfDef 参与过构建。
+
+```bash
+tsifdef build -p ./custom.tsconfig.json
+tsifdef build -p ./tsconfig.json -- --module commonjs --outDir dist
+```
+
+`-p`/`--project` 用于选择 tsconfig；`--` 之后的参数作为 tsc 选项覆盖它。切换
+Profile 会自动触发全量重编。不支持 `outFile` 和 composite references（`tsc -b`）。
+
+## 3. 编辑器（VSCode）
+
+让 `#if` 置灰、不再报错需要两部分：
+
+1. **VSCode 扩展**——安装 TSIfDef VSIX。它置灰并折叠未激活分支，并在状态栏显示
+   当前 Profile。
+2. **tsserver 插件**——随该 VSIX 一起发布，让语言服务忽略未激活代码。它通过
+   工作区 TypeScript 版本加载，因此需要将工作区指向其本地 TypeScript：
+
+```jsonc
+// .vscode/settings.json （或 *.code-workspace 的 settings）
+{
+  "typescript.tsdk": "node_modules/typescript/lib",
+  "typescript.enablePromptUseWorkspaceTsdk": true
+}
+```
+
+然后运行 `TypeScript: Restart TS Server`。之后未激活代码不再报错，
+`#if UNKNOWN_MACRO` 按 `false` 处理而非“未知宏”。
+
+升级扩展后同样要执行 `TypeScript: Restart TS Server`——正在运行的 server 会一直
+使用旧插件，直到重启为止。
+
+## 4. ESLint
+
+不接 TSIfDef 时，原始的 `#if` 行会被报成解析错误。ESLint processor 已包含在构建
+所安装的 `tsifdef` 包中，无需安装第二个包。
+
+将推荐配置放在项目现有的 TypeScript Flat Config 之后：
+
+```javascript
+// eslint.config.mjs
+import tsParser from "@typescript-eslint/parser";
+import tsifdef from "tsifdef/eslint-plugin";
+
+export default [
+  {
+    files: ["**/*.{ts,tsx,mts,cts}"],
+    languageOptions: { parser: tsParser },
+  },
+  tsifdef.configs["flat/recommended"],
+];
+```
+
+顶层仍使用项目正常的 `@typescript-eslint/parser`，让编辑器集成能够识别 TypeScript
+校验。
+
+不需要关闭任何规则。诊断报在真实行列位置，自动修复和编辑器快速修复正常工作，
+`prettier/prettier` 等格式化规则保持开启即可：未激活分支不会产生格式告警，而
+激活代码中的真实问题照常报告。TSIfDef 唯一会拦下的，是会覆盖 `#if` 行的那类
+修复——其诊断仍然照报，只是没有自动修复项。
+
+TSIfDef 支持 ESLint 8.57 和 9，以及 `@typescript-eslint/parser` 5 至 8。两者均为
+optional peer dependency，具体版本由宿主项目管理。
+
+### 旧版 `.eslintrc`
+
+旧配置系统会把 `tsifdef` 解析为名为 `eslint-plugin-tsifdef` 的包，因此需要将同一个
+包安装到该别名：
+
+```bash
+npm install -D eslint-plugin-tsifdef@npm:tsifdef
+# 离线使用发布产物时：
+npm install -D eslint-plugin-tsifdef@file:./tsifdef-<version>.tgz
+```
+
+```jsonc
+// .eslintrc.json
+{
+  "parser": "@typescript-eslint/parser",
+  "extends": ["plugin:tsifdef/recommended"]
+}
+```
+
+这一行同时配好 plugin、processor 和 `import/parsers`。如果项目同时 extends 了
+`plugin:import/typescript`，请把它放在 `extends` 的**最后**：那份配置会为相同
+扩展名注册 `@typescript-eslint/parser`，而 `eslint-plugin-import` 取先出现的
+那个 parser。
+
+若要手动展开：
+
+```jsonc
+// .eslintrc.json
+{
+  "parser": "@typescript-eslint/parser",
+  "plugins": ["tsifdef"],
+  "overrides": [
+    {
+      "files": ["*.ts", "*.mts", "*.cts", "*.tsx"],
+      "processor": "tsifdef/macros"
+    }
+  ],
+  "settings": {
+    "import/parsers": {
+      "eslint-plugin-tsifdef/parser": [".ts", ".tsx", ".mts", ".cts"]
+    }
+  }
+}
+```

package/LICENSE

@@ -0,0 +1,210 @@
+Tencent is pleased to support the open source community by making TsIfDef available. 
+
+Copyright (C) 2026 Tencent.  All rights reserved. 
+
+TsIfDef is licensed under the Apache-2.0.
+
+
+Terms of the Apache-2.0:
+--------------------------------------------------------------------
+Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Tencent
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.