Not an issue per se, but after looking at https://bocoup.com/weblog/advancing-the-open-web-through-test262 I thought it would be cool if we could run Babel with the tests as well? Not sure we have the capacity to deal with all the bugs (and many that might not be possible to fix, I figured it would be at least something to think about/try).
It seems as if we could use babel-node (http://babeljs.io/docs/usage/cli/#babel-node) instead of a node path and do something like test262-harness './test262/test/**/*.js' --hostType node --hostPath './babel/packages/babel-cli/bin/babel-node.js with the es2015 preset. Will probably need babel-polyfill as well.
Will look into it more but wanted to ask if there was anything I should look out for / discussion
Not an issue per se, but after looking at https://bocoup.com/weblog/advancing-the-open-web-through-test262 I thought it would be cool if we could run Babel with the tests as well? Not sure we have the capacity to deal with all the bugs (and many that might not be possible to fix, I figured it would be at least something to think about/try).
It seems as if we could use
babel-node(http://babeljs.io/docs/usage/cli/#babel-node) instead of a node path and do something liketest262-harness './test262/test/**/*.js' --hostType node --hostPath './babel/packages/babel-cli/bin/babel-node.jswith the es2015 preset. Will probably need babel-polyfill as well.Will look into it more but wanted to ask if there was anything I should look out for / discussion