You're probably looking for one of the following links:
Using Babel in your development pipeline will automatically transpile (convert) your JavaScript to be cross-browser compatible. Or, if you're using TypeScript, you can rest easy; your code is already getting transpiled.
Don't want to setup a transpiler (such as Babel/Typescript), or do you want to play with features not yet supported by your transpiler?
You can enable experimental ECMAScript features in your browser by going to chrome://flags/#enable-javascript-harmony and enabling the JavaScript Harmony flag. For some features, you may have to use Chrome Canary with the JavaScript Harmony flag enabled.
New JavaScript APIs are not usually covered by Babel, and will have their own Chrome flag.
Using Arrow functions
This question specifically mentioned using arrow functions. Arrow functions are now natively supported in all browsers except IE and Opera Mini. See caniuse.
It used to be a little difficult if you wanted to play with arrow functions. The below history shows what it took at different points in time to play with this feature.
1) At first, arrow functions only worked in Chrome Canary with the
chrome://flags/#enable-javascript-harmony
flag enabled. It looks
like this functionality was at least partially implemented by
version 39.
2) Then, arrow functions where made available in Google Chrome
behind the JavaScript Harmony flag.
3) And finally, in Google Chrome 45, arrow functions where enabled by
default.
You can expect a similar pattern to happen with other new ECMAScript features.