Move to UMD Definitions about typings HOT 8 CLOSED

See also dojo/meta#46 and dojo/meta#62

from typings.

@kitsonk does the move to UMD typings across our modules resolve this issue?

from typings.

It does for those packages, but wouldn't allow you to do it with Dojo 1 unless we converted to UMD.

from typings.

We could and would still use typings/typings for dojo 1

from typings.

We could, but it makes it difficult for people to namespace dojo, dijit, etc. and it doesn't reflecting, typing wise, what the actual code is doing, which would access the typings in a more modular way, exactly like the way Dojo 1 works.

This ticket isn't a priority.

from typings.

Think of the poor guys out there who are just trying to whip up a small web app here and there... they don't want to bother with a build tool.

With AMD modules, said guy can just concat up the necessary module files, probably with a simple shell script or a batch file.

With UMD modules, he needs to do a bunch of transformations.

So, use a better loader (one that handles all module formats) instead.

from typings.

@schungx I think you are mis-understanding. We aren't talking about UMD for Dojo 1, we are talking about the UMD definition format for TypeScript, where there is a file for each .js file as part of Dojo 1. When TypeScript acquires these types, they are scoped only to match the module they refer to and don't require a global namespace and would allow us to better model the actual behaviours of the Dojo 1 code.

from typings.

(Also, I should note that it was confusing that the TypeScript team refer to these non global definition files as UMD definition files, but we didn't have control over their choice of name)

from typings.