Main fixes:
- Identify dependencies from packages that only expose named exports (no
`.` export)
- Identify dependencies from exports containing wildcards (e.g.
`"./utils/*": "./src/utils/*.js`)
- Disallow identifying dependencies from restricted exports (e.g.
`"./foo": null`)
- Handle conditional exports (e.g. `"exports": { "import":
"./dist/index.js", "default": "./dist/index.js" }`
- Handle invalid `"exports": {}` (by not falling back to `main`)
- Handle projects included or not in package manager workspaces
## Current Behavior
## Expected Behavior
## Related Issue(s)
Fixes #29486
646 B
646 B
Interface: ProjectGraphProjectNode
A node describing a project in a workspace
Table of contents
Properties
Properties
data
• data: ProjectConfiguration & { description?: string }
Additional metadata about a project
name
• name: string
type
• type: "app" | "e2e" | "lib"