-
Notifications
You must be signed in to change notification settings - Fork 29.2k
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
TypeScript task detection is not cross-platform #68812
Comments
I think we should be able to normalize the path for |
Hey @alexr00, |
@gmertk are you still working on this? If not I'd like to help out. |
I was looking at this issue, I like the idea of https://code.visualstudio.com/docs/editor/tasks#_custom-tasks, where there is a section for windows specific command. Typescript task template can be updated to support something like this:
I had a hard time finding the typescript template definition! Any help in the right direction would be appreciated. @alpalla What do you think about this solution? Was yours similar? |
That seems like solving the wrong problem. Changing the pattern match from |
@alpalla Wanted to mention that I am working on it once I had a clear solution. Thanks for leaving this issue to me. I am glad to work on it till it's resolved. |
@NizamLZ It's great if you'll work on the problem, but please don't solve it by making unnecessary work for Windows cross-platform support. |
@TimMensch Ofcourse I won't. I will look into the suggestion you posted above. |
Issue Type: Bug
If your
tsconfig.json
is in a subfolder, the folder path has to match the system file separator (\ on Windows, / on Mac/Linux) in order for it to work.Steps to Reproduce:
The only workaround I've found is to create TWO tasks for each desired task, where one has forward slashes and the other backslashes. But a recent VS Code update made a warning box appear for those configurations every time I build or debug, which is annoying. Please address the underlying issue.
Honestly, this would be yet another situation where simply using forward slashes all the time would fix everything. This would also fix, for instance:
#35593
...a bug that's been around for a year and a half now. :(
VS Code version: Code - Insiders 1.32.0-insider (003521e, 2019-02-15T06:16:29.903Z)
OS version: Windows_NT x64 10.0.17134
System Info
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: enabled
surface_synchronization: enabled_on
video_decode: enabled
webgl: enabled
webgl2: enabled
The text was updated successfully, but these errors were encountered: