Typescript declaration files gets built in incorrect directory
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- build-system
Research direction
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.
Written by the indexing model from the issue text.
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.
- Dominant language
- JavaScript
- Stars
- 8.1k
- Forks
- 358
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from developit/microbundle
-
CSS
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
developit/microbundle#1002 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
developit/microbundle#789 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
developit/microbundle#1100 · 4 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
developit/microbundle#1094 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
developit/microbundle#1093 · 3 comments · 1 reaction ·
All issues in developit/microbundle
Similar issues
-
awaiting triage bug Causes friction Hop Gui P1 P2 Transforms
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
georgestephanis/p2026#40 ·
-
Enatega Customer and Rider app: Add-ons price is not visible to customer after order is placed. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Margaret-Petersen/food-delivery-app-clone-react-native#1981 ·