Be me
> find an eslint bug
> report it on their github
> ask to assign it to self
> start working on it
> spend half a day to find out the source of bug
> realises the bug is coming from a library eslint is using
> report it on the library's github
> ask to assign it to self

  • 19
    > repeat ad infinitum
  • 23
    >realise npm was a mistake and stop using JavaScript
  • 2
    In a comparable case with another code checker, I opened a bug ticket on their project. Nobody cared (as usually in open source). But I didn't even expect that because I just wanted the bug report ID as reference in my project why the reported issue is a false positive. Done.
  • 3
    @beegC0de interesting fact - almost every popular project is using this library. React, bootstrap, vue, jekyll, postman, graphql, netlify... You name a project and probably they are using this lib. So I went and checked some of these projects. Every goddamn project has this same bug.
  • 2
    @Fast-Nop I can relate. I have once raised a bug to Apple which was a blocker for my story. Guess what the status of that ticket is 💁‍♂️

    On a side note from my experience, *some* open source project issues are a lot likely to be looked upon by maintainers/contributors. The eslint bug which I raised was confirmed within an hour or so. The lib bug.. Well it has been 2 days now without any response...
  • 2
    Which package?
  • 2
    @Codex404 docsearch
  • 1
    You're the hero we need, but not the one we deserve
  • 2
    I'm now realizing that

    > while true

    would have been better. :/
  • 0
    And that's recursion without a termination condition!
Your Job Suck?
Get a Better Job
Add Comment