More information about es6: https://github.com/lukehoban/es6features
Labels |
Added:
?
?
|
We already do this for custom elements, so I suppose you can check that off.
yes and no... i checked the build scripts. we can at least refactor them (and probably get rid of browserify and use only babel-core instead as we said that we do not want to depend on bundlers anymore?).
Rename all Javascript files to *.es6.js and compile them. (OR: rename only the files that are rewritten in es6 to *.es6.js).
Let's do it the same way we're doing it in custom elements: .js is ES6, .es5.js
is dead code...
Let's do it the same way we're doing it in custom elements: .js is ES6, .es5.js is dead code...
we can do that, personally i like the *.es6.js approach more, because it does not change anything for the end user (he can continue to use validation.js, which will be compiled es5).
Hold on, is this (i mean the ES6 coded files) only for our eyes, only for devs?
If so we can do better, use the existing Joomla.webcomponents
loader and let the client side decide what type of js will be fetched...
In a first step i want to improve the current js code and be able to write es6 javascript. So the new .es6.js files are mostly for devs atm.
If we find a way to lazy load es6 modules, i would love to go a step further, but thats not a trivial task in joomla context.
Status | New | ⇒ | Discussion |
Category | ⇒ | JavaScript |
Labels |
Added:
J4 Issue
|
is this meta list being kept upto date
Closed due to lack of response
Status | Discussion | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2018-08-03 20:11:03 |
Closed_By | ⇒ | brianteeman |
We already do this (Babel) for custom elements, so I suppose you can check that off.