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
VS2015 "Error executing script" when typing import statement #11462
Thanks for reporting this. the error window is shown because you have enabled devMode at some point. if you feel these errors are in your way, you can disable it and the errors will be reported silently without the popup.
Hey nino-porcino (@nippur72) , I'm having trouble reproducing this issue. Can you post a more detailed repro? In particular, what does the directory structure look like?
Arthur Ozga (@aozgaa) opening the project on a different machine (same OS, VS and TS) does not give the error, so it must be something related to that particular machine, but I have no clue where to look for. Do you want me to try a fresh install of VS ?
Regarding the directory structure, the only strange thing is that node_modules is in the parent folder respect where the .sln / .csproj is:
I wasn't able to reproduce the issue using commit 31a55e6 of TypeScript on VS 2015 Update 3 with TypeScript 2.0 Beta installed (I enabled dev mode and pointed VS towards my local build of TypeScript).
If the problem persists on the same machine after pulling the latest version of TS off master and building, let me know an I will look into this further.
So just to clarify for those of us that want to develop without that error popping up every time we write an import statement, which is the appropriate course of action?
remove the latest version of TS for Visual and install v2.0.3 (worked)
(OR) edit the registry to disable devMode (which I didn't knowingly enable at any time) (didn't try)
I did the easy one and switched back to version 2.0.3 which seems to have stopped the issue for now but I worry that I'll be missing out on some important update that occurred since then... and there's no guarantee that I'll be able to update upon the next versioning
So just to clarify for those of us that want to develop without that error popping up every time we write an import statement, which is the appropriate course of action?
Switching off DevMod as noted earlier should make the pop up go away.
Activity
mhegazy commentedon Oct 10, 2016
Thanks for reporting this. the error window is shown because you have enabled devMode at some point. if you feel these errors are in your way, you can disable it and the errors will be reported silently without the popup.
mhegazy commentedon Oct 10, 2016
looks related to completion in imports recent changes. Arthur Ozga (@aozgaa) can you take a look.
aozgaa commentedon Oct 11, 2016
Hey nino-porcino (@nippur72) , I'm having trouble reproducing this issue. Can you post a more detailed repro? In particular, what does the directory structure look like?
nippur72 commentedon Oct 12, 2016
Arthur Ozga (@aozgaa) opening the project on a different machine (same OS, VS and TS) does not give the error, so it must be something related to that particular machine, but I have no clue where to look for. Do you want me to try a fresh install of VS ?
Regarding the directory structure, the only strange thing is that
node_modulesis in the parent folder respect where the.sln/.csprojis:aozgaa commentedon Oct 13, 2016
I wasn't able to reproduce the issue using commit 31a55e6 of TypeScript on VS 2015 Update 3 with TypeScript 2.0 Beta installed (I enabled dev mode and pointed VS towards my local build of TypeScript).
If the problem persists on the same machine after pulling the latest version of TS off master and building, let me know an I will look into this further.
nippur72 commentedon Oct 14, 2016
Arthur Ozga (@aozgaa) more clues:
If I use TS 2.0.3
there is no error.
But if I switch to nightly drops:
the error is back.
(The powershell command is from here).
Methodician commentedon Nov 1, 2016
So just to clarify for those of us that want to develop without that error popping up every time we write an import statement, which is the appropriate course of action?
remove the latest version of TS for Visual and install v2.0.3 (worked)
(OR)
edit the registry to disable devMode (which I didn't knowingly enable at any time) (didn't try)
I did the easy one and switched back to version 2.0.3 which seems to have stopped the issue for now but I worry that I'll be missing out on some important update that occurred since then... and there's no guarantee that I'll be able to update upon the next versioning
mhegazy commentedon Nov 1, 2016
Switching off DevMod as noted earlier should make the pop up go away.
aozgaa commentedon Nov 10, 2016
Still unable to repro. Would be happy to look into again this if you could link to a (minimal) reproducing project.