Sean Wood
Sean Wood
> I'm not sure it adds clarity by coloring the same things differently depending on context. I'm not so sure this is actually true. Consider the following: ```js const [item1,...
The _exact_ commmand was `lerna publish` and the _full_ error log (with sensitive details redacted) is as above. Anyway, as someone who is not 100% clued up on the internals...
I agree and I think that synchronises well with the idea of not ever publishing the same version of a module to NPM or any other registry more than once....
> TL;DR: Lerna won't support duplicate version tags, nor will it support publishing duplicate versions of a package to any registry, regardless of its (mis-)capabilities. I understand this and support...
@bradzacher This is all very well, but the reality is that these packages require significant amounts of context before approaching being the "champion". This is an issue that's cropped up...
@bradzacher Appreciate the response - Josh was very succinct about the symptom, but to create the link between that and the actual problem wasn't as easy. Instead the member analysis...
The background of JSX tags and generic argument syntax isn't new to me, that makes complete sense. To clarify, is https://github.com/typescript-eslint/typescript-eslint/blob/8ee0cbb0818392cc818b1c254dcec6e879f79a35/packages/utils/src/eslint-utils/rule-tester/RuleTester.ts#L127 the actual source of the issue? But I think...
Sorry @bradzacher, my snippet I linked was from the jest rule tester, not the actual plugin code. Can't digest an entire monorepo in one day. Let's continue the discussion in...
Honestly losing faith in actions - they're just not stable and powerful enough to run organisation-level workflows.
> Another option is to spin it as a separate package and remove it from pino altogether. It would be a shame to do this though, as there is plenty...