dependents / dependents/node-filing-cabinet

Node package.json exports field not understood.

Open
#170 1 comment 1 reaction 0 assignees View on GitHub
enhancement
Dominant language
JavaScript
Stars
87
Forks
47
PR merge metrics
No merged PRs in 30d

Description

Hi

I am importing from a node_modules package that uses the exports field to redirect to /dist

```json
"exports": {
"./*": "./dist/*"
}
```

However these dependencies are not found and show up in the nonExistent array.

```js
const nonExistent = []
const dependencies = dependencyTree.toList({
filename: filePathFull,
directory: process.cwd(),
nonExistent,
})
```

I have checked moving the imported files to the root of the package, and it does then find them - so it seems that the exports field is not understood.

I may be willing to work on this, if it's not a simple fix. Would it be a filing-cabinet issue?

Thanks

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the missing-dependency case with a node_modules package whose package.json exports maps './*' to './dist/*', then trace dependencyTree.toList and its nonExistent handling. Done means imports redirected through the exports field are resolved instead of added to nonExistent.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.