IMHO, the npm node packaging is just a mess -- I have several similar projects, and each has to pull in a HUGE pile of almost-identical dependencies, and not able to reuse between them at all. Whatever happening over there will not astonish me at all, including the infamous npm_left_pad_chaos <https://www.google.com/url?q=https%3A%2F%2Fwww.theregister.co.uk%2F2016%2F03%2F23%2Fnpm_left_pad_chaos%2F&sa=D&sntz=1&usg=AFQjCNGtlk1oK8v8nbhb1uBPNrOlvGrDiQ> problem.
Go packaging is far super than npm -- chaos at npm does not imply Go will suffer the same. On Wednesday, August 8, 2018 at 10:14:31 AM UTC-4, Manlio Perillo wrote: > > https://www.theregister.co.uk/2016/03/23/npm_left_pad_chaos/ > <https://www.google.com/url?q=https%3A%2F%2Fwww.theregister.co.uk%2F2016%2F03%2F23%2Fnpm_left_pad_chaos%2F&sa=D&sntz=1&usg=AFQjCNGtlk1oK8v8nbhb1uBPNrOlvGrDiQ> > > Manlio > > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
