javascript - AMD 加载器是否需要一种方法来启动除 "define?"以外的模块解析

Question

在关于我正在研究的最小 AMD 加载器的切线相关方面的讨论中，James Burke 写道:

There should to be some way to kick off the resolution of modules, besides just define(). define() calls by themselves should just register the existence of a module definition, but not immediately execute the factory function. That will more closely match expectations that people have from other loaders and how it more closely matches the behavior of dynamically loaded modules, whose factory functions are only called because they are part of a top level load dependency tree.

如果有人知道 AMD，那就是他。但是，我想知道他是否误解了我的装载机是如何工作的。它不会立即执行工厂，但会在调用 define 时立即开始解析依赖项。

本质上，我的加载器使用 define 来做同样的事情 RequireJS 使用全局 require 来做同样的事情，这对我来说很有意义，因为函数做的事情和它们的签名非常相似几乎相同。

---

在 new thread 中在 AMD implementers mailing list 上我回复:

The AMD loader I'm working on does not have a special way to kick off module resolution. The entire API is a global define function. When define is called, any dependencies are immediately loaded (if they haven't already started loading). When all dependencies in the chain are finished loading, the factory executes.

This has been good enough for my purposes so far, but is there some caveat I'm missing? What are some reasons for having a separate function to initiate module resolution, rather than simply resolving dependencies as soon as they're encountered and running factories as soon as all dependencies are met?

---

该列表没有太多访问量，所以我将它交叉发布在这里。我想从任何经常使用 AMD 加载器的人那里得到一些意见。您能预见到使用 define 而不是单独的函数来启动会出现什么问题吗？我完全尊重 James 对此的看法，但我想知道他是否已经习惯了 RequireJS 做事的方式，以至于其他任何事情似乎都是错误的，即使它在实践中运行良好。

回顾:

• 当 define 被调用时，列表中的所有依赖项开始加载(如果尚未开始)。

• 当所有依赖项准备就绪(具有导出值)时，工厂运行。

• 这就是整个 API，没有全局的require。

这种方法有什么问题(如果有的话)，除了不熟悉来自 RequireJS 的人之外？

---

更新:thread 上有一些事件这是起源的地方。到目前为止，这看起来相当于一个急切加载与延迟加载的场景。我仍然认为预加载可能是一种可行的方法，但希望从其他人那里获得更多意见。

---

回应对这个问题的反对意见:如果这个问题可以改进，请告诉我如何它可以改进。我已经尽可能清楚了；如果还有其他问题需要澄清，或者出于其他原因这个问题似乎质量不高，请提请我注意，我会解决它。

Answer 1

What are some reasons for having a separate function to initiate module resolution, rather than simply resolving dependencies as soon as they're encountered and running factories as soon as all dependencies are met?

是的，正如该线程中已经提到的那样，它用于延迟加载。 define register 回调以创建模块，而 require 实际上触发加载并创建模块实例。

AMD 就是围绕这个想法构建的，但它并不是必需的。 From the spec :

A global require() function is one that is available in the global scope, like define(). An implementation is not required to implement a global require, but if it does, the behavior of global require is similar to the behavior of the local require() function, with the following qualifications: […]

There is often an implementation-dependent API that will kick off module loading; if interoperability with several loaders is needed, the global require() should be used to load the top level modules instead.

构建一个 eager loader 很好并且符合规范。