Any intention to support AMD (asynchronous module definition)?

[jcbrand]

AMD together with module loaders such as require.js are increasingly being used for front end web development.

Has anyone at bootstrap considered supporting AMD in bootstrap's Javascript modules?

I'd be happy to help out if there is support for the idea. The UMD repo contains boilerplate examples of how one makes modules AMD compatible without losing backward compatibility.

[jcbrand]

I found this discussion: #14397

However, to be clear, using a require.js shim is not a solution in all cases. Specifically the use-case where you want to use something like $.noConflict to keep your (normally) global vars private. The shim only works with a global jquery variable.

[jcbrand]

Looking at other tickets mentioning AMD, looks like this has been added to the 4.0 milestone, although I can't find such a milestone.

In any case, I'll close this ticket. My offer to help still stands though.

[hnrch02]

We don't have a public v4 milestone yet. UMD support was planned for v3.2.0 (see #13772) but was reverted due to problems outlined in #13812.

[jcbrand]

@hnrch02 Would you be amenable to pull requests in this regard, or is there already internal work being done on this?

[hnrch02]

A pull request would make the most sense once public development of v4 has begun.

[morficus]

Just to clarify something - is UMD support planned for v3.4.0 or is it being held off until v4?

[cvrebert]

@morficus v4.