[
https://issues.apache.org/jira/browse/TAP5-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17950015#comment-17950015
]
ASF subversion and git services commented on TAP5-2803:
-------------------------------------------------------
Commit 07e0bb6de6c09aead03b69488c4eebeda7b3a74e 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=07e0bb6de ]
TAP5-2803: trying to figure out the suffix.mjs test failure
> 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)
