Martin Muñoz

Yeah, that makes sense. I think that in the scenario where you're only interested in changing the crate's own version it would be beneficial to treat all the other crate...

I suspect YUI DOCs would be a welcome PR, even if just fleshing out input/outputs.

I like it too.

Do you have an example? The AST transform is fairly straightforward and only touches stable parts of the AST so I would be surprised if it broken in any version....

Sounds good to me. I believe this project is no longer in use in the ember-cli ecosystem (instead we've moved to https://github.com/chadhietala/babel-plugin-debug-macros), but I'm happy to merge a PR with...

I was going to suggesting adding it twice but I beat me to it. I'd hope that it is supported in Babel 6! We can definitely tweak the options for...

@Turbo87 I mildly disagree, but if you code it I'll merge it. Having the plugin support multiple feature flags seems overly coupled to me. It would be as if `Object.keys`...

I like @Turbo87's implementation where the feature flags are shared among all the imports. This has landed on the babel-5 branch but I'll leave it open until it lands on...

In the application I am working on I was able to resolve this bug by changing ```json "workspaces": [ "packages/**/*" ], ``` to ```json "workspaces": [ "packages/@org1/*", "packages/@org2/*", "packages/*" ],...

I would like to find a path towards dropping snake-casing conventions entirely. EDIT: Looks like there's an RFC: https://github.com/emberjs/rfcs/issues/556.