Detect module flags in filenames

[matthewrobb]

When compiling files on disk or loading files from script's in the browser detect the following patterns:

*.amd.six
*.node.six
*.umd.six
*.yui.six

Compile them out using the specified module type as the module wrapper.

[insidewhy]

I think I'd prefer a command line flag to select the module system rather than via a file name extension.

I think it's highly unlikely to be mixing module systems in source (rather people would be selecting UMD for cross-environment code).

For me... I'd want it to use UMD in the general case and then compile all the scripts together into a single file for the web, but then UMD + r.js can also handle that without the need for six.

[insidewhy]

Embedding the type in the extension also implies a certain kind of inflexibility.

I might want to compile the same project to both AMD and NODE (for whatever reason I might hate UMD).

Then I'd have to keep switching the filenames?

[matthewrobb]

It would be inflexible but wouldn't be the ONLY way to do it, just an optional way to override. I was working with YUI and realized UMD can't possibly hit every module style and it would be nice to support as many as possible without creating a mega shim. By default I imagine it would do UMD, the file extension stuff would just be ANOTHER method.

Other options would be comment embedded annotations, compile time config file (.sixconfig?), and providing config to the browser script.

[insidewhy]

I see cool! Sounds like a good idea and seems like you've already
thought everything through well :)

For my uses it'll be exclusively:

• nodejs: UMD modules
• web development: UMD modules
• web delivery: modules combined and minified as a single resource.

I need to add another patch to add module names to the UMD generator, as
it stands r.js can't combine the files which breaks my third scenario.
My fault!

Cheers, James

On Fri, Nov 02, 2012 at 07:34:57am -0700, Matthew Robb wrote:

It would be inflexible but wouldn't be the ONLY way to do it, just an
optional way to override. I was working with YUI and realized UMD can't
possibly hit every module style and it would be nice to support as many
as possible without creating a mega shim. By default I imagine it would
do UMD, the file extension stuff would just be ANOTHER method.

Other options would be comment embedded annotations, compile time
config file (.sixconfig?), and providing config to the browser script.

--
Reply to this email directly or [1]view it on GitHub.
[J6T91GIPIyhU-8ti4GCGP5vfNxJyDS9_dR-JYJhJ00OYcWruqhAWW4U387hs_2Rv.gif]

References

1. Detect module flags in filenames #64 (comment)

http://chilon.net