mtc fails to externalize .d.marko deps when another .d.marko is imported through a .d.ts file
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- devtools
Research direction
Start with the linked reproduction and its src/components/test.marko, src/types.d.ts, and tsconfig files, then trace how mtc resolves tag-discovered .d.marko dependencies through TypeScript imports. Confirm the failure with the reported setup; done means the dependency is externalized without the tsconfig file-list error.
Written by the indexing model from the issue text.
Description
Version
mtc 6.1.3
Description
mtc fails to externalize tag-resolved .d.marko dependencies when another .d.marko is imported through TypeScript module resolution.
Reproduction
Repro: https://github.com/caseycarroll/mtc-externalize-err
src/components/test.markouses a marko component through auto tag discovery.src/types.d.tscontains a type import from an unrelated .d.marko file- tsconfig contains
"include": ["src"],
mtc throws:
File '/Users/cacarroll/code/repros/mtc-externalize-err/node_modules/.pnpm/@[email protected]_@[email protected][email protected][email protected]/node_modules/@ebay/ebayui-core/dist/components/ebay-icon/icons/ebay-search-20-icon/index.d.marko' is not listed within the file list of project '/Users/cacarroll/code/repros/mtc-externalize-err/tsconfig.json'. Projects must list all files or use an 'include' pattern.
importing the type of the same path in the test.marko does not throw the same error.
- Dominant language
- TypeScript
- Stars
- 44
- Forks
- 12
- Avg merge
- 41m
- Merged PRs (30d)
- 9
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
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 marko-js/language-server
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
marko-js/language-server#596 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
marko-js/language-server#581 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
marko-js/language-server#240 · 2 comments ·
Maintainers usually reply within 1 day
All issues in marko-js/language-server
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
rohitg00/agentmemory#1428 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
boxlite-ai/boxlite#1729 ·
Maintainers usually reply within 1 day
-
detectors enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
SM260845/readme-gen#1 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
angular/angularfire#3774 ·
Maintainers usually reply within 2 days