browser version of sweet.js

[disnet]

Currently we have some node dependencies but would be nice to run in the browser. Need to factor out the require calls and do a little cleaning.

[ryanseddon]

Just tried running it through browserify but it died on trying to find a parse-js module. This is on windows, will try on osx later.

[disnet]

Same happens on osx, unless escodegen is installed globally I think. Would probably be best if we could avoid using browserify though.

[iammerrick]

If you make this run in the browser, I will make an AMD loader for it... :-) Just let me know when!

• Merrick

[disnet]

It should work in the browser with AMD now.

[iammerrick]

You beautiful man. Thank you. I can't wait to make this sucker an AMD loader. :-D

[iammerrick]

What do you think of the sweet object having a method to convert the AST back into the compiled JS. This would mean consumers of sweet.js on the client don't have to talk to escodegen directly. It's really more of a sweet.js dependency then a sweet.js consumers dependency...

Example Problem: https://github.com/iammerrick/require-sweet/blob/master/src/sweeten.js#L4

Also, I think the dependencies parser, expander & escodegen ought to be relatively required so as not to require a certain folder structure or set of AMD path entries of sweet.js consumers. underscore is exception here as it is typically a named dependency.

Example Problem: https://github.com/iammerrick/require-sweet/blob/master/example/index.html#L12-14

I would be happy to make a pull request with these updates if you are open to it?

[disnet]

Yeah, that all sounds great.

[iammerrick]

Pull requested.!

[disnet]

Awesome!