Unable to resolve index.tsx dependencies
Nobody has claimed this yet.
- #116 by @SyMind — closed without merging
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, typescript
- Domain
- tooling
Research direction
Reproduce the issue with the components/lib index.tsx file containing export * lines and inspect how the dependency resolver handles components/lib and the reported nonExistent partials. Compare the behavior with madge issue 128 and the available debug output. Done means index.tsx dependencies resolve without the empty filepath warning.
Written by the indexing model from the issue text.
Description
I'm having trouble running this package over dependencies that include in index.tsx file as I'm getting the error:
tree skipping an empty filepath resolution for partial: components/lib +29ms
My index.tsx in components/lib just consists of export * from ___ lines.
I saw this similar issue here: https://github.com/pahen/madge/issues/128 but it didn't seem to have a solution. Any ideas on this?
In the debug output i'm seeing:
tree deduped list of nonExistent partials: [
'components/lib',
...
'../..' ]
- Dominant language
- JavaScript
- Stars
- 776
- Forks
- 82
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 dependents/node-dependency-tree
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
question
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
question
Difficulty 3/5 1-2 days Newbie friendliness 25/100
dependents/node-dependency-tree#152 · 2 comments ·
-
Why is precinctOptions.includeCore always false?May be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
All issues in dependents/node-dependency-tree
Similar issues
-
ai core enhancement good first issue testing
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
cli: `studio --request <missing file>` answers with a raw ENOENT/EISDIR instead of a clear errorOpenbug good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
laaielichter/Ai-edit-studio#81 ·
Maintainers usually reply within 1 day