Tapestry 5.4 require.js modules

[Kristian Marinkovic]

Hi all,

why are tapestry's requirejs modules nested in an anonymous javascript
function:

(function() {
   define(['jquery'], function($) {
   })
}).call(this);

isn't it enough to just write define(...., function() {})? Is there a
reason for this additional scope?

cheers,
Kris



BTW, i just migrated an existing T5.3.7 application to T5.4-beta-2 with
almost no hassle. i'm really impressed.