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
{{ message }}
Repository navigation
Doesn't support rename refactoring with importing from a module (yarn workspaces) #31825
changed the title [-]Doesn't support module rename refactoring with importing from modules (yarn workspaces)[/-][+]Doesn't support rename refactoring with importing from modules (yarn workspaces)[/+]on Jun 8, 2019
changed the title [-]Doesn't support rename refactoring with importing from modules (yarn workspaces)[/-][+]Doesn't support rename refactoring with importing from a module (yarn workspaces)[/+]on Jun 8, 2019
Activity
[-]Doesn't support module rename refactoring with importing from modules (yarn workspaces)[/-][+]Doesn't support rename refactoring with importing from modules (yarn workspaces)[/+][-]Doesn't support rename refactoring with importing from modules (yarn workspaces)[/-][+]Doesn't support rename refactoring with importing from a module (yarn workspaces)[/+]RyanCavanaugh commentedon Jun 13, 2019
The behavior you see is what was requested from multiple other users
wclr commentedon Jun 13, 2019
What do you mean? What behavior? You mean refactoring
./packages=>@app/module? Ok I could agree with this.The problem is that it doesn't rename
test=>test2and that is a bug definitely.RyanCavanaugh commentedon Dec 3, 2025
Closing language service bugs related to the 6.0 implementation. For more information, see #62827