Skip to content
This repository has been archived by the owner on Aug 3, 2023. It is now read-only.
This repository has been archived by the owner on Aug 3, 2023. It is now read-only.

What about adoption to AMD? #48

Open
@qfox

Description

I don't see much changes in modules.require vs System.import, except in AMD dependencies can be file names.

But there are some differences in define:

modules.define(
  {String} moduleName,
  [{Array.<String>} dependencies,]
  {function (
    {function ( resolution, [{Error} error] )} provide,
    {Array.<*>} ...imports,
    [{*} prev]
  )} declarationFunction
);

What if we will compare dependencies.length with declarationFunction arity and decide with mind on that how to call declarationFunction?

It will help us to use modules as AMD module loader.

Is there any other problems or differences between current ym functionality and AMD standard?

Why I ask? Because ES6 modules comes to us. And I think about using ymodules for ES6 modules.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions