Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/58632

Could you run OVERWRITE=true yarn jest to re-generate the fixtures?

Rather make ES6-compatible since in this branch present Object.getOwnPropertySymbols.

@zloirock based on the feedback in the original issue, as well as the fact the ESLint rule to prefer .includes() was turned off in the helpers, it seemed like this was the correct course of action. But in addition to that, there isn't a guarantee that simply because Symbols (and therefore Object.getOwnPropertySymbols) is available that the .includes() method is available. If Symbols are polyfilled but the array prototype is not, this would still create failures. By assuming both must exist if one exists, its coupling unrelated capabilities.

I realize that seems like a niche scenario, but considering the cost of closing that gap definitively is basically zero, not sure what benefit there is with that coupling.

@tquetano-netflix I didn't say it's wron way. It's just a question of the title -)

@zloirock Ah! My apologies for the misread, it's late for me. 😅 Feel free to make the title whatever makes the most sense, @nicolo-ribaudo has already updated it once.