[
https://issues.apache.org/jira/browse/TAP5-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14113483#comment-14113483
]
Jochen Kemnade commented on TAP5-2350:
--------------------------------------
I'm not currently working on it. I've added {{AMDWrapper}} as a way to get
around the issue and it works fine in my webapps (also with the bootstrap
libraries that Tapestry ships). But I'm not sure where to go from here. We
could refuse to add shimmed libraries to a stack. Or we could deprecate
{{JavaScriptModuleConfiguration}} and switch to AMD wrapping altogether. It's
probably not a good idea to have shimming and wrapping coexist anyway.
> 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)
