You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whereas there are performance benefits to running ES6 natively in browser, we should provide both ES6 and legacy JS versions of component JS files. In DCF core, we'll keep an ES6 copy of the component's JS file. In DCF Starter, we'll use Gulp to copy the ES6 version to the frontend project. We'll also transpile a legacy version. The directory structure will be as follows:
Whereas there are performance benefits to running ES6 natively in browser, we should provide both ES6 and legacy JS versions of component JS files. In DCF core, we'll keep an ES6 copy of the component's JS file. In DCF Starter, we'll use Gulp to copy the ES6 version to the frontend project. We'll also transpile a legacy version. The directory structure will be as follows:
/
js/
dist/
dcf-lazyload.es6.js
dccf-lazyload.js
mycustomjs.es6.js
mycustomjs.js
src/
mycustomjs.es6.js
We'll handle ES6 detection in a follow-up task in DCF core: digitalcampusframework/dcf#302
The text was updated successfully, but these errors were encountered: