-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot rename/move directories. #750
Comments
This used to be a problem when we rolled our own tsserver, but we've stopped doing that, and now Angular LS relies completely on stock tsserver for file / project management. I wonder if we could reproduce the same problem using just tsserver. |
One area we need to investigate is whether NON_POLLING_WATCHER is used. It is the default watcher, and is known to be more efficient and avoid problems like this. |
This happens to me also. Is it related to when finally changing folder, the imports wont update? |
Still seeing this in
|
Is there any workaround, its super annoying if the refactor is need to be done by hand. |
still no solution... 😔 |
Angular language service use non-pooling directory watchers and it does not allow to rename directories. Currently, it's not possible to change this behavior by |
The non-polling watchers are used to improve performance, but now that there's built-in option to configure watch mode, we should remove the environment variable. |
`TSC_NONPOLLING_WATCHER` was used back in the early days to improve file watcher performance, but it prevents files / directories from being moved / renamed. Since TS now provides built-in option to configure file watcher, this environment variable is no longer needed. See https://www.typescriptlang.org/docs/handbook/configuring-watch.html Fix angular#750
`TSC_NONPOLLING_WATCHER` was used back in the early days to improve file watcher performance, but it prevents files / directories from being moved / renamed. Since TS now provides built-in option to configure file watcher, this environment variable is no longer needed. See https://www.typescriptlang.org/docs/handbook/configuring-watch.html Fix #750
`TSC_NONPOLLING_WATCHER` was used back in the early days to improve file watcher performance, but it prevents files / directories from being moved / renamed. Since TS now provides built-in option to configure file watcher, this environment variable is no longer needed. See https://www.typescriptlang.org/docs/handbook/configuring-watch.html Fix #750
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
…atchOptions `TSC_NONPOLLING_WATCHER` was used back in the early days to improve file watcher performance, but it prevents files / directories from being moved / renamed. Since TS now provides built-in option to configure file watcher, this environment variable is no longer needed. See https://www.typescriptlang.org/docs/handbook/configuring-watch.html The watch options used are derived from the user defined options in their `tsconfig` combined with the default options provided to the project service via `setHostConfiguration` ([code reference](https://github.com/microsoft/TypeScript/blob/f7ef1540d3c10fb282d1d433d9f2850b28391169/src/server/editorServices.ts#L2985-L2989)). As noted in the documentation for configuration watch options, the default when no watch options are provided falls back to `fs.watchFile` with `250ms` for any file. This would cause the performance issues as seen in angular#1310. Fixes angular#750
…atchOptions (#1323) `TSC_NONPOLLING_WATCHER` was used back in the early days to improve file watcher performance, but it prevents files / directories from being moved / renamed. Since TS now provides built-in option to configure file watcher, this environment variable is no longer needed. See https://www.typescriptlang.org/docs/handbook/configuring-watch.html The watch options used are derived from the user defined options in their `tsconfig` combined with the default options provided to the project service via `setHostConfiguration` ([code reference](https://github.com/microsoft/TypeScript/blob/f7ef1540d3c10fb282d1d433d9f2850b28391169/src/server/editorServices.ts#L2985-L2989)). As noted in the documentation for configuration watch options, the default when no watch options are provided falls back to `fs.watchFile` with `250ms` for any file. This would cause the performance issues as seen in #1310. Fixes #750
…atchOptions (angular#1323) `TSC_NONPOLLING_WATCHER` was used back in the early days to improve file watcher performance, but it prevents files / directories from being moved / renamed. Since TS now provides built-in option to configure file watcher, this environment variable is no longer needed. See https://www.typescriptlang.org/docs/handbook/configuring-watch.html The watch options used are derived from the user defined options in their `tsconfig` combined with the default options provided to the project service via `setHostConfiguration` ([code reference](https://github.com/microsoft/TypeScript/blob/f7ef1540d3c10fb282d1d433d9f2850b28391169/src/server/editorServices.ts#L2985-L2989)). As noted in the documentation for configuration watch options, the default when no watch options are provided falls back to `fs.watchFile` with `250ms` for any file. This would cause the performance issues as seen in angular#1310. Fixes angular#750
…atchOptions (#1323) (#1326) `TSC_NONPOLLING_WATCHER` was used back in the early days to improve file watcher performance, but it prevents files / directories from being moved / renamed. Since TS now provides built-in option to configure file watcher, this environment variable is no longer needed. See https://www.typescriptlang.org/docs/handbook/configuring-watch.html The watch options used are derived from the user defined options in their `tsconfig` combined with the default options provided to the project service via `setHostConfiguration` ([code reference](https://github.com/microsoft/TypeScript/blob/f7ef1540d3c10fb282d1d433d9f2850b28391169/src/server/editorServices.ts#L2985-L2989)). As noted in the documentation for configuration watch options, the default when no watch options are provided falls back to `fs.watchFile` with `250ms` for any file. This would cause the performance issues as seen in #1310. Fixes #750
Describe the bug
In windows, the ng language service plugin locks all folder/subfolders of the workspace.
I tracked this lock down with LockHunter.exe:
It points to the VSCode subprocess for
angular.ng-template.0.901.3\server
.This lock causes renaming directories to fail with:
Error: EPERM: operation not permitted, rename '<source>' -> '<target>'
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Folder renaming should work.
Logs
Not applicable.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Version info:
The text was updated successfully, but these errors were encountered: