Closed jamestalmage closed 9 years ago
@twada I'm going to bump to espower 1.1.0 in package.json. Unless you publish in the next few seconds my next push is going to fail CI. Just re-trigger via Travis web page once the release is cut and it should pass again.
Also, just FYI - I don't know if you are an Intellij user, but if so, I hope you find this useful: https://github.com/jamestalmage/intellij-code-to-string-js
@jamestalmage I've released espower 1.1.0 and restarted Travis build.
Also, just FYI - I don't know if you are an Intellij user, but if so, I hope you find this useful: https://github.com/jamestalmage/intellij-code-to-string-js
Wow this is so useful for creating our tests! Yes, I'm using WebStorm (and yeah, Emacs :stuck_out_tongue_winking_eye:).
woot! Green!
@jamestalmage Thank you for your great contribution! I'm going to cut a new release (as 1.2.0) soon.
awesome! Thanks!
Just released power-assert-formatter 1.2.0. Thank you for your great contribution!
From what I can tell, there is no way to get esprima to parse a yield statement that is not wrapped in a generator function.
To work around this, I do the following:
This will require additional modifications on the instrumentation side of things before the output looks correct (my test will need to be modified at that point). The result of the yield is not captured.