Métriques du dépôt

Stars: (48 455 stars)
Métriques de merge PR: (Merge moyen 6j 17h) (9 PRs mergées en 30 j)

Description

Suggestion

🔍 Search Terms

references path relative

✅ Viability Checklist

My suggestion meets these guidelines:

[ x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x ] This wouldn't change the runtime behavior of existing JavaScript code
[ x] This could be implemented without emitting different JS based on the types of the expressions
[x ] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x ] This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion

Both https://www.typescriptlang.org/tsconfig#references and https://www.typescriptlang.org/docs/handbook/project-references.html aren't specific about what the string in path is relative to (the current tsconfig, the current working directory, rootDir, etc)

💻 Use Cases

I'm writing some build scripts around invocations of tsc with a lot of linking, aliasing, etc and I don't want to put absolute paths in the generated tsconfig files

Guide contributeur

Direction de recherche: Examinez le manuel TypeScript et la documentation tsconfig pour déterminer à quoi le chemin dans les références de projet est relatif (tsconfig actuel, répertoire de travail, rootDir, etc.) et proposez une mise à jour clarifiant cela.
Stack technique: typescript
Domaine: documentationdeveloper experience
Type d'issue: Documentation
Difficulté: 1
Temps estimé: Moins d'une heure
Statut d'activité: Active
Clarté: Claire
Prérequis: TypeScript basics
Accessibilité débutant: 90