WebStorm automatically modifies nx-angular-config (checked into Git)

I’m experiencing an issue with WebStorm and the nx-angular-config file in my project. This file is part of our repository and is shared among the team. Each time I open the project in WebStorm, changes are automatically made to this file without any manual action on my part.

Context:

  • Editor: WebStorm 2024.3
  • Project type: Angular with an NX workspace
  • File: frontend/.idea/nx-angular-config (checked into Git)
  • Behavior: WebStorm modifies the file automatically when I open the editor.
  • Repository: Shared with a team, so unintentional changes to the file are problematic.

What I’ve tried:

  1. Reviewing WebStorm settings, but I couldn’t find any relevant options.
  2. Checking installed plugins – I don’t have anything installed that explicitly modifies NX configurations.

Questions:

  1. Is there a setting in WebStorm that automatically modifies NX or Angular-related configuration files?
  2. How can I prevent WebStorm from modifying this file without removing it from version control?
  3. Has anyone else encountered similar issues with NX workspaces in WebStorm?

Edit:

  • Corrected the file path from “frontend/nx-angular-config” to “frontend/.idea/nx-angular-config”
0
8 comments

I can tell for sure that Webstorm itself doesn't modify Angular or NX configuration files in any way.

What kind of changes are made to the file?

0

The changes have to do with the modules that we have I think. Also, if it makes any difference, the file is located in the .idea folder. I corrected it in my post.

0

So it appears to be one of the IDE configuration files. Looks like it's generated and updated by one of the NX plugins (Nx Console?). Do you have any of them installed?

0

Yes, that's the only NX plugin that I have installed (when I do a search on “NX”).

0
Thanks for clarifying it. I'd suggest contacting the plugin developers (https://github.com/nrwl/nx-console/issues) on this.
0

Thank you for your help. I've submitted an issue here.

1

After updating the file in our repo with these changes, we have no issues any more 👍🏻

0

Please sign in to leave a comment.