#general
- e
enough-analyst-54434
10/09/2015, 7:56 PMDoes packages.json handling by npm support any form of templating? - e
enough-analyst-54434
10/09/2015, 7:58 PMIt would be nice to be able to transition to a global set of versions in packages.json by having users, one by one, say typ='{typ}' - b
bright-dinner-81701
10/09/2015, 7:58 PMno it doesnt template - e
enough-analyst-54434
10/09/2015, 7:58 PMAnd pants - when loading packages.json and converting in mem to build, would have 3rdparty versions templated if folks are ready to reference them - w
witty-crayon-22786
10/09/2015, 7:58 PMargh. i think https://rbcommons.com/s/twitter/r/2937/ is too large to rush to fix before a release. getting up into the 15-20 files and some public interfaces affected range - w
witty-crayon-22786
10/09/2015, 7:59 PM@enough-analyst-54434: how's about a smaller hotfix there, then i'll follow up with this - e
enough-analyst-54434
10/09/2015, 7:59 PMHow often do you change tools? - e
enough-analyst-54434
10/09/2015, 7:59 PMsg - w
witty-crayon-22786
10/09/2015, 7:59 PMvery often - w
witty-crayon-22786
10/09/2015, 7:59 PMwe're iterating on improving zinc and sbt - w
witty-crayon-22786
10/09/2015, 8:00 PMk... will see how big this gets, and then do an expedient fix if it's too large. - b
bright-dinner-81701
10/09/2015, 8:14 PM@enough-analyst-54434: yeah unfortunately no templating, which means if we introduced it into as a Pants-only thing devs lose the ability to work with normal npm by itself - b
bright-dinner-81701
10/09/2015, 8:14 PMits very easy to have NPM emit warnings that your npm_remote_module deps dont match what you have in package.json tho - b
bright-dinner-81701
10/09/2015, 8:15 PMbut not require there to be node_remote_module deps at all (they can be only in package.json)… but if you declare them, you get a warning if they fall out of sync, letting you implicitly communicate that the org is moving to a new version without requiring it - e
enough-analyst-54434
10/09/2015, 8:15 PMAnd pants could do similar I guess. If a pants repo was in lock-down mode, pants could go as far as failing a packages.json with a non-compliant 3rdparty dep rev - b
bright-dinner-81701
10/09/2015, 8:15 PMsorry easy to have Pants emit warnings* - b
bright-dinner-81701
10/09/2015, 8:15 PMnot have NPM emit warnings - b
bright-dinner-81701
10/09/2015, 8:16 PMyes - b
bright-dinner-81701
10/09/2015, 8:16 PMyes, that is a good point - b
bright-dinner-81701
10/09/2015, 8:16 PMit could even fail it if you wanted to enforce that everyone in your org stay on a certain version of a 3rd party module - b
bright-dinner-81701
10/09/2015, 8:17 PMso node_remote_module becomes less about a resolvable target and more like an enforecement mechanism you can opt into for targets - b
bright-dinner-81701
10/09/2015, 8:17 PMlike if you only declare 3rd party modules in your package.json, then you get those - e
enough-analyst-54434
10/09/2015, 8:17 PMSomething like that - yes. There could be a buildgen that re-wrote dependencies in packages.json - b
bright-dinner-81701
10/09/2015, 8:17 PMif you also declare a dep in BUILD on node_remote_module, you get Pants checking your package.json against it - e
enough-analyst-54434
10/09/2015, 8:17 PMYou want to write a new module, forget the 3rdparty versions exactly, so leav them unconstrained, run buildgen --rewrite-ok - e
enough-analyst-54434
10/09/2015, 8:18 PMand it fills them in for you - e
enough-analyst-54434
10/09/2015, 8:18 PMwhere this time buildgen re-emits your packages.json with versions filled in - e
enough-analyst-54434
10/09/2015, 8:18 PMOK 18 ways it seems like to get halfway to a controllable system - e
enough-analyst-54434
10/09/2015, 8:19 PMWork to do! - b
bright-dinner-81701
10/09/2015, 8:20 PMhaha