jsfx.js can be used as both an IIFE and a node module

[mtmckenna]

Hello! I'm pretty jazzed on jsfx and looking to use it in an app that uses NPM modules to handle dependencies, and so it would be convenient if jsfx could be packaged as an NPM module as well.

In this pull request, I updated jsfx.js to be able to be executed as either an IIFE (as it is currently) or as an NPM module. I based my changes on this post from NPM and this blog post. The update should not break any compatibility with previous versions of jsfx.

If these changes work for you and you're interested, it'd be extra handy if you wouldn't mind publishing jsfx to NPM.

In case it's useful, I also created a demo app that is your index.html using the Node module version of jsfx.

Please let me know if you have any questions or thoughts!

Thank you!

McKenna

[egonelbre]

Tabs, tabs everywhere :D

Otherwise it looks good.

Also, is it possible to avoid assigning version numbers to npm modules? It does not make sense for this library -- or rather it's more dangerous to put one. You should be depending on a particular version rather than 1.+... Although the API is stable, the results may not be.

[mtmckenna]

Sounds good! Happy to convert the spaces to tabs. One thing--it looks like the original file uses tabs rather than spaces. Would you like me to convert the whole file? The reason I didn't do that originally was to make the diff prettier. =)

As for the version number, it looks like it's required to publish on NPM. We could set the version number fairly low if that'd help (like 0.0.1)? What do you think?

[egonelbre]

Would you like me to convert the whole file?

Not sure what you mean? I meant that the diff you submitted had spaces, but these should have been tabs -- nothing more. The same for the json file. :)

(PS: I really don't care about the tabs/spaces, as long as it is consistent, and for whatever reason I ended up using tabs in this project.)

As for the version number, it looks like it's required to publish on NPM. We could set the version number fairly low if that'd help (like 0.0.1)? What do you think?

1.0.0 is fine then, as it would be more aligned with versioning spec.

[mtmckenna]

Ah--I misinterpreted and though you preferred spaces everywhere. =) Changed the spaces to tabs. Let me know if you'd prefer I squashed the commits into one!

[egonelbre]

I will take a look at publishing to npm tomorrow.

[mtmckenna]

Awesome, thank you very much!

[egonelbre]

I published it under loov-jsfx, because I wasn't able to get scoped packages working.

[mtmckenna]

Thank you!!