-
-
Notifications
You must be signed in to change notification settings - Fork 631
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Specifying deps outside of BUILD files (aka "dep inference") #6449
Comments
Thanks Ny... will get to this this week. |
In the current state of node source-level dependencies, users have to specify dependencies both in the |
Refreshed the branch here: master...twitter:stuhood/dep-inference . The largest blockers for landing this afaict (labeled with TODOs in the branch), are:
|
I think that doing this in a more principled is going to require getting |
@stuhood closed? |
Heck yes. Thank you @Eric-Arellano. |
The canonical way of specifying dependencies in Pants is through the BUILD file. Currently this limits the entry to barrier for wiring in new tools/plugins that natively has its own way of tracking dependencies. Such is the case for Node.js dependency management through NPM/Yarn (#6332). There can be an argument that BUILD should be the source of truth, but I feel that is impractical given the resources it may take to support something like node.js package management. There should be a way to infer dependencies outside of BUILD files that is easily extensible to other formats.
The text was updated successfully, but these errors were encountered: