TypeScript Without Compilation
- 🦕 Deno allows running TypeScript code using
deno run(documentation) - ts-node
Yarn Plug’n’Play error without using Yarn
An issue I had with installing dependencies complaining about Yarn Plug’n’Play even though I’m not using Yarn.
[ERROR] Could not resolve "rfdc"
quartz/util/path.ts:3:17:
3 │ import rfdc from "rfdc"
╵ ~~~~~~
The Yarn Plug'n'Play manifest forbids importing "rfdc" here because it's not listed as a
dependency of this package:
../../../.pnp.cjs:37:31:
37 │ "packageDependencies": [\
╵ ~~
You can mark the path "rfdc" as external to exclude it from the bundle, which will remove this
error and leave the unresolved path in the bundle.
The issue was resolved using this GitHub comment pointing out that there might be lingering files from Yarn if it was ever installed.
Articles
- Using TypeScript on a large scale, the focus of the article is on the time it takes to run type-checking
- The TypeScript compiler is single-threaded
- Bazel build files and TSConfig files are auto-generated using Gazelle to declare dependencies automatically (and remove unnecessary dependencies)
- Tooling on top of the build system to get a better understanding of the system as a whole
- Using measurements to focus efforts on the longest dependency chains
- Isolated declarations speed up the process because projects need to only type-check the declarations of their dependencies. Requires explicitly defining types that could otherwise be automatically inferred. This can already be automatically inferred, automated tooling, such as ts-fix, can take care of this instead of updating the code manually.