You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2014/06/10 16:26:02 UTC

[jira] [Commented] (TAP5-2350) JavaScript library with module shim config is loaded twice if module is added to a stack

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

Jochen Kemnade commented on TAP5-2350:
--------------------------------------

For example, the effect can be observed when adding the {{bootstrap/dropdown}} module to the {{@Core}} JavaScript stack and {{require}}ing from client-side code. The library is included in the stack and also loaded stand-alone in a later request. 

> JavaScript library with module shim config is loaded twice if module is added to a stack
> ----------------------------------------------------------------------------------------
>
>                 Key: TAP5-2350
>                 URL: https://issues.apache.org/jira/browse/TAP5-2350
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: Jochen Kemnade
>              Labels: javascript, stack
>
> When a shim config is defined for a JavaScript library and the resulting "module" is added to a JavaScript stack, the raw library will be added to the stack resource (without a define statement). But under normal circumstances, it will never be used as it is added without any module wrapper code.
> When the library is required (via the shim module) from another module, requirejs loads it again.



--
This message was sent by Atlassian JIRA
(v6.2#6252)