48cd50a550
<!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior <!-- This is the behavior we have today --> Local Nx plugins in the new TS setup can't be resolved properly if they aren't built first. Graph plugins can't be built either because the graph is needed to run a task, but the plugin must be built to construct the graph. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> Local Nx plugins should work in the new TS setup. A custom resolution is added to resolve the local plugin artifacts from the source. It will try to use a `development` condition from the `exports` entry in `package.json` if it exists. If it doesn't, it will fall back to guess the source based on the artifact path and some commonly known/used source dirs: `.`, `./src`, `./src/lib`. ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #
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: "lib" | "app" | "e2e"