Cannot redeclare block-scoped variable. The Reason behind the error and the way to resolve it.

Few days back I was trying to write a script in my Visual Studio Code IDE, where I was trying to declare and initialize a variable with the keyword let.

But, I was faced with an error. Part of the error message was, Cannot redeclare block-scoped variable.

VS Code showing the TypeScript error Cannot redeclare block-scoped variable var1, ts 2451, pointing at a second declaration in main.js

So, I dug a bit into it to find out the reason behind the error. What I found was:

Because, the let keyword is block scoped and unlike var, it can not be re-declared or reassigned within the same block.
After Transpiling, the var1 variable of my main.ts file is also now available on the Transpiled main.js file as "var var1".
Right now after the Transpilation there are essentially two variables with the same name var1; one of which is in the main.ts which is declared as let (remember let is not redeclared or reassigned) and another one is in main.js
So naturally visual studio code displays the error on main.ts file because the variable in there, is declared with the let keyword.
As a result it won't allow to Transpile the file and displays Cannot redeclare block-scoped variable "variable name".

How to resolve?

Typescript is moduler and each module has it's own block. So, basically if you could somehow enclose the variable which is declared as let within it's own module, the error will be resolved because now your let variable is in it's separate block.

To achieve this, simply type export on the top of your script or additionally you can type export {}. Now you will see that the error is resolved.

The same main.ts file with export {} added above the let declaration, which clears the error

Hope this article helps you finding out and resolving the issue. Thanks a bunch! for reading out.

Need this inside a real product? ARITS does web app and platform engineering.

Need extra engineers, or a team to run the build?

Tell us the shape of the work and your deadline. You will get a straight read on what it takes and what it will cost, from a team that has shipped 400+ projects out of Dhaka and London.

More from our blog

A road forking toward two map pins, one for Bangladesh and one for India

Engineering Strategy

Outsourcing to Bangladesh vs India: Where Each One Wins

We build software in Dhaka, so we sourced every number here, including the two where Bangladesh loses to India. A comparison you can check yourself.

Build vs Buy for HRMS: modular blocks (custom build) versus a sealed product box (off-the-shelf)

Engineering Strategy

Build vs buy HRMS: when custom beats off-the-shelf

Off-the-shelf HRMS or a custom build? How to decide by company structure, payroll, and scale, and what building one actually takes.

Engineering Strategy

Software handover checklist: could you deploy without us?

What a software handover should leave you with: the assets you already hold, three tests the vendor must pass, and the one clause worth reading.

Engineering Strategy

Staff augmentation vs outsourcing: which fits your project

Staff augmentation or outsourcing? How each model works, what each costs you in management time, and when to pick which. From the engineers at ARITS.