Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Supporting CommonJS Module Loader plugin extensnion (or improve it to fit your needs) #1

Closed
temsa opened this issue May 10, 2011 · 3 comments
Assignees

Comments

@temsa
Copy link

temsa commented May 10, 2011

We start to have a lot of AMD implementation, and that's great. BTW, each implementation has it's own way to handle loading plugins, and it's not a good idea.

Making loader plugin a standard provided by Curl will improve the number of total plugin available for it and in general for AMD, helping to its diffusion as a standard for loading modules (at least on the browser side).

If the spec isn't satisfying, it could be a good idea to contribute to it also ;)

@ghost ghost assigned unscriptable May 10, 2011
@unscriptable
Copy link
Member

Hey temsa!

curl.js's plugins all adhere to the CommonJS Modules/LoaderPlugin proposed spec. RequireJS's don't, yet.

There's no proposed standard for the names of plugins. I think this would also be important in the near future. For example, I think we should reserve the following names for plugins that are likely to be used by most loaders:

text! -- load a text file
css! -- load a css file as a link
i18n! -- load a translation string bundle
js! -- load a non-module javascript file

Is this what you mean?

-- John

@temsa
Copy link
Author

temsa commented May 10, 2011

Hi ! and thank you for your great talk at #JSConf, was part of the attendees :)

Sorry, I probably overlooked your plugin code while searching for all AMD implementations that don't follow this spec (BTW, curl is not listed in CommonJS wiki as an implemention of this spec ;) ). I just try to move people to have real standards about this. in some way I would have liked a better approach (worked a bit with Wes Garland for CommonJS Module/2.0 spec some months ago, and proposed some syntax, following more or less @danwrong guidelines), allowing for more innovative possibility regarding syntax, but still i prefer something standard, rather than per implementation.

I know you've tweeted about the new mailing list Jame has made (I guess, didn't verified it was him, but at least he advertised it on twitter end commonjs mailing list), I just put the url if some other people interested by this topic would want to join : https://groups.google.com/group/amd-implement

@temsa temsa closed this as completed May 10, 2011
@unscriptable
Copy link
Member

Hi temsa. I remember you. You asked some good questions about ES/Harmony Modules. :)

You wrote:

BTW, curl is not listed in CommonJS wiki as an implemention of this spec

Thanks! I fixed that just now.

Looking forward to working with you on AMD and modules.

-- John

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants