Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Learn more about Collectives

Teams

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Learn more about Teams

First of all, I've already seen the other posts about error TS1005. Same error code, but totally different.

A simple let x: number; will generate the error TS1005 during compilation. It's not about a missing semicolon as what the error message says, but the compiler does not recognize the let keyword. I read that maybe because of an outdated compiler.

Here's my typescript version installed using npm install -g typescript

  • TypeScript version: 2.5.2
  • Compiler (tsc) version: 1.0.3.0
  • Maybe somebody can help?

    No. This is an error from Typescript because npm installs the wrong version. I opened an issue about it . @StockUberflow Please support it. Yairopro Jan 31, 2018 at 14:10

    Your installation is wrong; you are using a very old compiler version (1.0.3.0).

    tsc --version should return a version of 2.5.2.

    Check where that old compiler is located using: which tsc (or where tsc ) and remove it.

    Try uninstalling the "global" typescript

    npm uninstall -g typescript
    

    Installing as part of a local dev dependency of your project

    npm install typescript --save-dev
    

    Execute it from the root of your project

    ./node_modules/.bin/tsc
                    Hi sir, solved it. Thank you. The key is which tsc or where tsc. Found out there was another version of tsc in C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\. I just removed the old one from the path.
    – StockUberflow
                    Sep 25, 2017 at 7:37
                    I was using a slightly older version of tsc which led to not existing issues. I updated the global tsc and now it is okay.
    – Seagull
                    Aug 28, 2018 at 12:51
                    This worked awesome. I was using npx tsc <filename> to compile. Weird that npx would use an outdated version?
    – colefner
                    Jul 4, 2019 at 5:49
    

    On Windows you can have in your PATH

    PATH = ...;C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\; ...
    

    remove it from PATH env, then

    npm install -g typescript@latest
    

    it worked for me to solve the

    "TypeScript error TS1005: ';' expected"

    See also how to update TypeScript to latest version with npm?

    This answer solved the issue for me. I think you have to restart your PC. My OS was windows 7. – Ehsan Shekari Apr 25, 2019 at 11:00

    npm checks if tsc command is already installed.

    And it might be, by another software like Visual Studio. If so, npm doesn't override it. So you have to remove the previous deprecated tsc installed command.

    Run where tsc to know its bin location. It should be in C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\ in windows. Once found, delete the folder, and re-run npm install -g typescript. This should now install the last version of typescript.

    I faced the same error. After banging my head for half an hour, I found one Romeo bracket hanging around without his Juliet LOL...!(the opening and closing brackets were mismatching) Please check all your brackets to avoid such errors.

    That is, the first one has [[], instead of normal array []

    TS error was not clear enough, and it showed error in the last line with } );

    Hope this helps.

    I had today a similar error message. What was peculiar is that it did not break the Application. It was running smoothly but the command prompt (Windows machine) indicated there was an error. I did not update the Typescript version but found another culprit. It turned there was a tiny omission of symbol - closing ")", which I believe The Typescript is compensating for. Just for reference the code is the following:

    [new Object('First Characteristic','Second Characteristic',
    'Third Characteristic'*] 
    * notice here the ending ")" is missing.
    

    Once brought back no more issues on the command prompt!

    Stupid issue with minor mistake;

    i was trying

    const quizType = computed(() => rootState.quizzes.quiz
    const res = await noAuthApi.getQuizzes(quizType)
    

    and the issue was, i missed the closing bracket. it should be like

    const quizType = computed(() => rootState.quizzes.quiz)
    const res = await noAuthApi.getQuizzes(quizType)
    

    in my case I'd the 'function' keyword. I'd to remove it.

    Bad:

    export class CustomValidators {

    static function myFunc(x: string) { console.log(x) }

    Good:

    export class CustomValidators {

    static myFunc(x: string) { console.log(x) } Your answer could be improved with additional supporting information. Please edit to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers in the help center. – Sumit Sharma May 27, 2022 at 14:01 // No Error constructor( @Inject('USER_SERVICE') private readonly userService: UsersService, ) { }

    There may be a conflict with both of the packages "tsc" & "typescript" due to the fact that they both use the same command tsc index.ts

    tsc is deprecated, hence you should only use typescript:

    > npm install -g typescript

    > tsc ./index.ts

    Thanks for contributing an answer to Stack Overflow!

    • Please be sure to answer the question. Provide details and share your research!

    But avoid

    • Asking for help, clarification, or responding to other answers.
    • Making statements based on opinion; back them up with references or personal experience.

    To learn more, see our tips on writing great answers.

    typescript error ts1005 ' ' expected i tried all possible solutions and resources and didn't work See more linked questions