dist folder can't be un-excluded
I recently installed PhpStorm on my new machine and when I clone my repository from GitHub, the ‘dist’ folder is showing as excluded and I can't seem to get PhpStorm to un-exclude the folder. I'm tried right-clicking on the folder and under ‘Mark Directory As’ I pick the ‘Non Excluded’ option but the folder remains excluded as ‘Non-Project Files’. Under the Directory settings, the ‘dist’ folder is not listed in the excluded list. I've tried deleting the project and cloning the project again but I've encountered the same issue.
Please sign in to leave a comment.
Hi Alexander Jones, this is a known issue that will be fixed in the upcoming PhpStorm updates. Please check https://youtrack.jetbrains.com/issue/WEB-60460 for details.
Our apologies for the inconvenience.
distandbuildfolders are auto-excluded as a result of changes introduced in WEB-68312. We will see how it can be improved. Please feel free to follow WEB-70291 to be notified about updates.In the meantime, there is a workaround: you can press double Shift, type
registry, and open theRegistry...window. In this window, disable theexclude.generated.files.in.javascript.package.rootskey.I have the same problem.
In my project, I most often have to work with the “dist” folder, and the fact that your program is now broken is not cool at all.
I've updated to 2024.3.4 and this problem is still relevant. This is the second update in which this problem is not fixed. Shouldn't such bugs be fixed first?
This problem occures also in WebStorm and other JetBrains Products. In first hand, why is this a setting by default? You are excluding by default /dist and /build folders in javascript projects, but wtf is a javascript project? You are deciding this again for me, instead of leaving this my option.
This stuff took me two whole days to fix this, because there was no clue, why these folders where excluded. And now I find out about this magic registry.
When right-clicking the folder and choosing “not exclude” NOTHING HAPPENS! Where is the notification saying, that you have this magic registry, where you are disabling user specific settings on a global scale. This is just wrong and makes this product in this case just wortless and a pain.
Please follow WEB-70291 and linked tickets for the updates.
It would really help, if you could say “sorry!” in the first hand or explain, why you are doing so.
Please see my comment above for the explanation and workaround.