Changes to TypeScript definitions in locally linked Node package are not refreshed by ReSharper in referencing projects
We're using ReSharper Ultimate 2017.3.1 in Visual Studio 2017 (15.5.2)
We have a NodeJS project that contains TypeScript code shared by a couple of Aurelia CLI projects, transpiled into AMD format.
We use the 'yarn link' command to link this project as a local package into the node_modules folders of the referencing application projects.
ReSharper correctly finds the local package and sees the type definitions that are exported from the shared project, everything is working fine there.
However, what we are seeing is that if we make any definition changes to the shared project and rebuild, ReSharper doesn't pick up the changes made to that package until we restart the entire solution, which is pretty inconvenient for development. Normal TypeScript compilation is fine.
Is there a way to force ReSharper to reload node_modules so it picks up any changes made to packages, or to make this happen automatically?
Please sign in to leave a comment.
Note that unloading / reloading just the referencing projects in Visual Studio also works, but it would be good to not have to do this all the time.
Also, the Visual Studio TypeScript Language Service does pick up changes made to definition files - it's only ReSharper that doesn't.
Hello Spiper!
Sorry for delay in responding.
Our developer investigated the problem and turns out it's actually a bug.
We are planning to fix it in ReSharper 2018.1 version.
Thank you.
Here's corresponding issue reported - https://youtrack.jetbrains.com/issue/RSRP-468199
Please feel free to comment or vote for it.
Thank you.