Isn’t that one of (the other being to isolate the issue) the reasons we do minimal reproducible fiddles/codepens/stackblitz with dummy content and css?
Ask for a minimum reproducible sample without all the fluff? I know, wishful thinking…
It‘s what I do when I file Webkit/Safari issues just because the odds of it getting solved increase 🙂
I always try my hardest to create a minimal reproduction.
But a lot of the times, once I strip away everything that makes my app be my app, the bug no longer manifests so I just don't open an issue because I'm never sure if that means I'm using it wrong or I'm just missing the uncovered edge case
But that‘s great place to be in, no? Basically you have a state where it works and another where it doesn’t… now you just have to bisect until you reach that point where you added something that causes the bug…
And yeah „just“ doing heavy lifting here. 🙂
The unfortunate part of this way is it puts the burden back on the maintainers. They want to help, and maybe there is a bug but they should not be spending more of their free time even reading your issue.
It’s not your fault, this is the system we have, but for larger projects the number of issues like you describe is quite high. Takes enough time that we have a whole triage team setup to try and help address these for @expressjs.bsky.social.
If I had to give any advice here, it is to not open your issue until you I have had time to diagnose. If there is an existing issue of a similar nature and you can add more details than are already present then comment in it.
This is just another way of saying "yeah I don't feel like sandboxing my report causa I'm lazy AF and I want you to debug my code via a weird and contextless-text-description" 🤷♂️
At some point, it is not really easy to repro full context env of the bug. Enterprises have Private Registries, a lot of logic is reused in private modules. We are really challenged with this. Laziness is not the reason 100% of the time.
Not in a fresh context. But in past I've tried to bring parts of private modules which were related in a bug. Then again fell short grabbing more parts of other private packages I didn't have access to. At some scenarios it is not that a dev would not want to provide repros.
Comments
It‘s what I do when I file Webkit/Safari issues just because the odds of it getting solved increase 🙂
But a lot of the times, once I strip away everything that makes my app be my app, the bug no longer manifests so I just don't open an issue because I'm never sure if that means I'm using it wrong or I'm just missing the uncovered edge case
And yeah „just“ doing heavy lifting here. 🙂
It's proven to be misleading in current form.