If int foo = 'bar' is allowed, that would be far more confusing than the "oops, i'm writing a different language" one you describe.
If it isn't allowed, then you're talking about adding a type system, which is a vastly more complex ask than "let's add some aliases for let" (not to mention, what about const? both variants? pick one?)
I can certainly feel your pain. Switching between languages is always a little difficult. The amount of times I forget semicolongs in Java, and yet try to add them in code in other languages that don't need them is astronomical. But, trying to unify the syntax between languages, even when it conceptually doesn't make sense doesn't seem like a great solution. In fact, I don't think there's a good solution to this problem, the problem is at the very heart of the idea of having different languages.
I am not talking about adding a type system (there is already one: TypeScript), I am talking about adding syntax sugar that will achieve two thinkgs:
Make copying code from one language to another easier
Will allow programmer to visually use types IF HE DESIRES SO.
What I am suggesting is that the compiler would not check the validity of the statements. You can write "int var = 'abcd' " and the compiler wouln't do a peep. "int", "string", "String" or "boolean" equals "let". That's it, nothing more.
If somebody thinks this is confusing, he has the freedom not to use this syntax and stick to the "const" and "let".
Neither of those two sound like an improvement to me. Copying code from another language that won't behave the same is a terrible thing to make easier, and using types that aren't checked doesn't strike me as having any benefit.
This is not a good idea. JavaScript is dinamically typed, while those languages where you write int or string to declare variables are statically typed.
If you want a “JavaScript with static types” I encourage you to take a look at TypeScript. I guess it is exactly what you’re looking for.