| 17:24 | <bakkot> | ljharb: I am going through ecmarkup's deps (mostly sparked by noticing it was using chalk v1, lol), and |
| 17:24 | <bakkot> | what does safe-publish-latest actually do? |
| 17:24 | <bakkot> | I don't know enough about how npm works to understand the description |
| 17:25 | <ljharb> | Makes sure if we publish a backport, that it’s not published as latest. Given that we don’t seem to ever do that with ecmarkup, it’d be fine to remove the dep and the prepublish scripts, but it also only runs once at publish time ¯\_(ツ)_/¯ |
| 17:25 | <ljharb> | i just reflexively add it to every package i maintain because the lack of it has caused painful problems in the past |
| 17:26 | <bakkot> | make sense |
| 17:26 | <bakkot> | I don't mind keeping it, I was just curious |
| 17:27 | <bakkot> | that said it is responsible for a distressingly high fraction of the (dev) dependency tree of ecmarkup, via inclusion of yargs |
| 17:28 | <bakkot> | someday, util.parseArgs |
| 19:41 | <ljharb> | definitely will use parseArgs once it’s stopped evolving |