带有babel es2015预设的webpack是否会解决IE 11上的关闭问题？

Question

If I write a for loop using the let keyword to declare my loop variable, and I pass that variable to a

 for(let x=0;x<5;x++){ setTimeout(function(){console.log(x);},1000); } 

call, it will not work in IE 11 because IE 11 does not support ES2015. But I can write this code in Typescript, compile, and use Babel to output to supposedly IE11-compatible code. Will Babel successfully recognize and fix this?

I realize this is relatively simple to test myself once I get an environment all set up but I kinda feel like this might just be the tip of the iceberg for what Babel can and cannot do. Just wondering if someone knows off the top of their head if or how this works and if there are some related closure-related things that Babel just cannot transform. Thanks in advance. ---Edit--- Passing the variable 'x' into the function actually yields an undefined error so I guess I was breaking some other rule there. But, after removing the anonymous function parameter to create a proper closure on 'x', I find that the Babel conversion does NOT properly log the value 0,1,2,3... At this point I guess I would disagree with those who are saying that it does properly convert this scenario. Or I am totally missing something. (Thanks to the first person who replied with the link to babeljs.io/repl ! Very cool.)

Answer 1

Make sure you are using env aka es2015 preset.

in babelrc :

{
   "presets": ["env"]
}