You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I get closing the issue if there is not enough information, but locking those issues after 2 weeks is counterproductive, as this prevents tracking if an issue is still present and from reviving the original issues with more information and being able to get feedback from everyone involved. It also causes unecessary duplicates which we as users have to sort through all of them to find relevant information to avoid repeating the same thing and finding the cause.
They seem to all be the same issue, and for now no solution as been provided (as I also got the error today after upgrading a nuxt project and vite went from v7 to v8, I believe it could be an issue with multiple versions of vite coexisting as I now have both v7 in nested deps and v8 in the root dep)
I understand the locking might be to avoid noise to maintainers reviewing the issues. But clearly it's having the opposite effect as now you get multiple duplicates and the issue is still not figured out. Meaning a new issue will have to be filled again and again. Which dillutes availability and knowledge in the thread. One big thread for one issue is better in every way and the locking of issues is preventing those threads from forming on long standing issues.
2 weeks is nothing in the lifecycle of an issue. If you want to lock older issues, please consider doing this only after more than 1 year. Thank you.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I get closing the issue if there is not enough information, but locking those issues after 2 weeks is counterproductive, as this prevents tracking if an issue is still present and from reviving the original issues with more information and being able to get feedback from everyone involved. It also causes unecessary duplicates which we as users have to sort through all of them to find relevant information to avoid repeating the same thing and finding the cause.
Example: relatively recent issues
#12845
#18137
#12344
#12344
#20997
They seem to all be the same issue, and for now no solution as been provided (as I also got the error today after upgrading a nuxt project and vite went from v7 to v8, I believe it could be an issue with multiple versions of vite coexisting as I now have both v7 in nested deps and v8 in the root dep)
I understand the locking might be to avoid noise to maintainers reviewing the issues. But clearly it's having the opposite effect as now you get multiple duplicates and the issue is still not figured out. Meaning a new issue will have to be filled again and again. Which dillutes availability and knowledge in the thread. One big thread for one issue is better in every way and the locking of issues is preventing those threads from forming on long standing issues.
2 weeks is nothing in the lifecycle of an issue. If you want to lock older issues, please consider doing this only after more than 1 year. Thank you.
All reactions