Skip to content

VS2015 "Error executing script" when typing import statement #11462

Closed

Description

@nippur72

TypeScript Version: typescript@2.1.0-dev.20161008
Visual Studio: VS2015CE Update 3

Code

import { Store } from ".    <--- caret is placed here

Actual behavior:
When typing the dot . at line 1, the following error window appears in visual studio:
error executing script

Activity

  1. mhegazy commented on Oct 10, 2016

    @mhegazy
    Contributor

    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.

  2. mhegazy commented on Oct 10, 2016

    @mhegazy
    Contributor

    looks related to completion in imports recent changes. Arthur Ozga (@aozgaa) can you take a look.

  3. aozgaa commented on Oct 11, 2016

    @aozgaa
    Contributor

    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?

  4. nippur72 commented on Oct 12, 2016

    @nippur72
    Author

    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:

    project
    + node_modules
    + src
       + myproject.sln
       + mytsfiles.ts   
    
  5. aozgaa commented on Oct 13, 2016

    @aozgaa
    Contributor

    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.

  6. nippur72 commented on Oct 14, 2016

    @nippur72
    Author

    Arthur Ozga (@aozgaa) more clues:

    If I use TS 2.0.3

    npm install typescript@latest 
    powershell .\VSDevMode.ps1 14 -tsScript node_modules/typescript/lib
    

    there is no error.

    But if I switch to nightly drops:

    npm install typescript@next
    powershell .\VSDevMode.ps1 14 -tsScript node_modules/typescript/lib
    

    the error is back.

    (The powershell command is from here).

  7. modified the milestones: TypeScript 2.1, on Oct 27, 2016
  8. Methodician commented on Nov 1, 2016

    @Methodician

    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

  9. mhegazy commented on Nov 1, 2016

    @mhegazy
    Contributor

    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.

  10. aozgaa commented on Nov 10, 2016

    @aozgaa
    Contributor

    Still unable to repro. Would be happy to look into again this if you could link to a (minimal) reproducing project.

  11. locked and limited conversation to collaborators on Jun 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    BugA bug in TypeScriptFixedA PR has been merged for this issueNeeds More InfoThe issue still hasn't been fully clarified

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions