developit / developit/microbundle

Typescript declaration files gets built in incorrect directory

Ouverte
#854 8 commentaires 6 réactions 0 personnes assignées Voir sur GitHub
Langage dominant
JavaScript
Étoiles
8.1k
Forks
358
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

I have three projects, **Project A**, **Project B**, and **Project C** that looks something like this:

## Project A
```
// package.json
{
"main": "build/index.js",
"module": "build/index.modern.js",
"types": "build/index.d.ts",
"source": "src/index.ts",
}
```
The project outputs the declaration file correctly inside `build/index.d.ts`
## Project B
```
// package.json
{
"main": "build/index.js",
"module": "build/index.modern.js",
"types": "build/index.d.ts",
"source": "src/index.ts",
"dependencies": {
"@my-workspace/project-a": "^1.0.0",
},
}
```
The project **INCORRECTLY** outputs the declaration file inside `build/project-b/src/index.d.ts`.
## Project C
```
// package.json
{
"main": "build/index.js",
"module": "build/index.modern.js",
"types": "build/index.d.ts",
"source": "src/index.ts",
"dependencies": {
"@my-workspace/project-b": "^1.0.0",
},
}
```
This project fails to build because it can't find the declaration file for `@my-workspace/project-b`.

## Issue
In my actual project I have 12 packages in a yarn workspace / lerna environment. The issue randomly happens for some projects and not others even though they all have the same microbundle and typescript config setup.

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Piste de recherche

Start with the package.json declarations and the src/index.ts entry points in Projects A, B, and C, then inspect the microbundle and TypeScript configuration used across the Yarn workspace/Lerna packages. Reproduce the differing declaration output and trace why Project B writes build/project-b/src/index.d.ts. Done means every package emits its declaration at the configured build/index.d.ts path and downstream packages can resolve it.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
typescript
Domaine
build-system
Type d'issue
Bug
Difficulté
4/5
Temps estimé
3-5 jours
Activité
À l'abandon
Clarté
Plutôt claire
Accessibilité débutants
35/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.