[jira] [Commented] (TAP5-2803) Add support for JavaScript/ECMAScript 6 modules

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TAP5-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17949170#comment-17949170 ] 

ASF subversion and git services commented on TAP5-2803:
-------------------------------------------------------

Commit 70cfe2922e98936c78bafde670cb445172a8c84e in tapestry-5's branch refs/heads/javax from Thiago H. de Paula Figueiredo
[ https://gitbox.apache.org/repos/asf?p=tapestry-5.git;h=70cfe2922 ]

TAP5-2803: support for global per-thread ES module config callbacks

> Add support for JavaScript/ECMAScript 6 modules
> -----------------------------------------------
>
>                 Key: TAP5-2803
>                 URL: https://issues.apache.org/jira/browse/TAP5-2803
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>            Reporter: Thiago Henrique De Paula Figueiredo
>            Assignee: Thiago Henrique De Paula Figueiredo
>            Priority: Major
>             Fix For: 5.10.0
>
>
> Right now, while Tapestry has built-in support for including JavaScript files and Require.js modules in components, pages and mixins, it has none for JavaScript/ECMAScript  6 [modules|[https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Modules].] This makes using them in Tapestry webapps hard to do.
> To avoid confusion with Require.js modules, which are referred as "modules" in the Tapestry support for them (@Import's module attribute, JavaScriptSupport require() methods), JavaScript modules will be referred in the new code as "esModule" (as in ECMAScript module, ECMAScript 6 being the JavaScript standard which defines how modules work).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)