-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Support ES6/ES2015 Features #14506
Comments
(This is to consolidate every little, individual inquiry on ES6 request) |
Hi!
Thanks in advance |
I also would like to know when this is going to happen. |
Hi. Answering to your questions:
|
Loki won't be tested against Node 0.10 anymore, since it is officially at its EOL. This is also necessary to move to a Promise based API. Because PhantomJS currently does not support ES6, a Promise polyfill is used in the browser tests in the meantime (see ariya/phantomjs#14506).
|
2.5 beta release now supports ES2015! Give it a try! 🙌 |
How do I install beta release? |
After spending around 30 minutes looking around (GitHub, Bitbucket, existing documentation) and even looking at the commit history (on master and 2.1 branches), I still don't know where the 2.5 beta source code is. Where is the latest and greatest (even if unstable) codebase for PhantomJS (for those of us who want to try building it ourselves)? |
Would someone with the project be able to release the 2.5 beta on npm under a |
@vitallium Binaries of the latest beta version for windows (phantomjs-2.5.0-beta-windows.zip) does not follow naming conversion for executable path as in previous versions. It breaks phantomjs-maven-plugin, which uses this template For linux it's ok. |
@arokhmistrov Whoops. Updated! Thank you. |
Any plans to create a ruby gem for the 2.5 beta? Super eager to experiment with it in a ruby project, but not having any luck implementing the downloads. Thanks! |
I'm on trusty:
I downloaded
Looks like, I think, it wants gcc 4.9 but only up to 4.8 is available. I can't use PPAs, which seems to be the way the internet suggests getting gcc 4.9 on trusty. |
@arantius yes, we follow Webkit plans to drop |
@Bard182 For Ruby gems of 2.5, try building the branch at colszowka/phantomjs-gem#97. The gem needs testing on Windows, so it would be useful to have someone verify it works. |
phantomjs doesn't support es6 (ariya/phantomjs#14506)
* replace phantomjs with headless_chrome phantomjs doesn't support es6 (ariya/phantomjs#14506)
...for compatibility with PhantomJS. ariya/phantomjs#14506
Seems that it is now viable with the updated community QtWebKit. |
Object.assign is introduced in ES6 (2015) which is not supported by PhantomJS. Replace it with the equivalent _.extend function to prevent frontend tests from failing. 1. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/assign#Specifications 2. ariya/phantomjs#14506
Object.assign is introduced in ES6 (2015) which is not supported by PhantomJS. Replace it with the equivalent _.extend function to prevent frontend tests from failing. 1. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/assign#Specifications 2. ariya/phantomjs#14506
Object.assign is introduced in ES6 (2015) which is not supported by PhantomJS. Replace it with the equivalent _.extend function to prevent frontend tests from failing. 1. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/assign#Specifications 2. ariya/phantomjs#14506
Object.assign is introduced in ES6 (2015) which is not supported by PhantomJS. Replace it with the equivalent _.extend function to prevent frontend tests from failing. 1. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/assign#Specifications 2. ariya/phantomjs#14506
Object.assign is introduced in ES6 (2015) which is not supported by PhantomJS. Replace it with the equivalent _.extend function to prevent frontend tests from failing. 1. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/assign#Specifications 2. ariya/phantomjs#14506
ES2015 (also colloquially known as ES6) will be possible with the new effort towards version 2.5 (see #14458 for details).
When building PhantomJS with the latest QtWebKit, PhantomJS will get all the latest JavaScriptCore support for ES2015. See the blog post ES6 Feature Complete for more details.
At that time, all examples should be also modernized to use the latest ES2015 syntax.
The text was updated successfully, but these errors were encountered: