Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

anyway yeah i really think the “still works with npm by itself thing” is important

Is anyone actively working on getting source_roots out of BUILD files and into some other format?

prior art in buck to just match directory paths.

anything with 'src' or 'test' as the name?

define patterns like `src/java`, and then the first in the path wins

and in our case, allow plugins to include patterns maybe.

<@U04S45AHA>: in the current Pants (from my last commit) i’m achieving that by having Pants blow away all the deps fields in package.json an existing source package.json before it re-emits the package.json with the deps filled in according to the BUILD targets, but under this it can now preserve the 3rd party ones

I was also thinking of putting a file called SOURCE_ROOT in a dir, marking it as a source root

and if that file isn't empty, then it contains the target types allowed in that dir

How do you do your 1600 source roots now?

<@U04S45AHA>: but i at least included in the last examples commit one in which i put a fully-functional package.json <https://github.com/pantsbuild/pants/blob/master/contrib/node/examples/src/node/server-project/package.json>

<@U051221NF>: no. we have 1600 source roots

Not much of a proposal, but on the file itself: <https://github.com/pantsbuild/pants/issues/2144>

Yes, but how do you tell pants where they are?

also: <https://groups.google.com/d/msg/pants-devel/dAn_XexmXQw/omyFLAzQrVYJ>

<@U06A03HV1>: how do you tell pants about your 1600 source roots?

via explicit maven_layout calls all over the place