search

componentjs / require2

builder2's require implementation
8 stars 3 forks source link

Consider adding module meta-data to modules entry #4

Open dominicbarnes opened 10 years ago

dominicbarnes commented 10 years ago

I just came across a case where it would be extremely helpful to have meta-data about a package available to my script. For example, when using clipboard-dom, you need to give a path to the swf file. However, I currently have to manually specify a path like: /public/component/clipboard-dom/v0.0.5/ZeroClipboard.swf

Since CSS URLs get rewritten, it seems reasonable to allow a JS file to pick up an asset URL like this. Could each registered component include something like a "path" (or at least name/version?)

jonathanong commented 10 years ago

Not sure how to do this without making it a clusterfuck. Haha. It should be added to the component.json somehow and let the builder handle it

dominicbarnes commented 10 years ago

Hmm, maybe the builder can automatically include the source component.json as well? (or would that be weird too?)

jonathanong commented 10 years ago

I would say the easiest thing to do is have require.assets = {} lookup. The builder should map the asset name somehow to a URL you could use Ajax on. Including component.json files would be way too noisy

dominicbarnes commented 10 years ago

Ok, I think that's reasonable. I'll start working on this