global cli broken if there is any babel version mismatch
jamestalmage opened this issue · comments
If there is any difference in the babel-version installed globally, vs that installed locally, you get:
TypeError: Plugin "babel-plugin-espower" is resolving to a different Babel version than what is performing the transformation.We could use fallback-cli to always use the local install of ava if there is one. Things might get weird if they had no local install, but did have babel-runtime installed locally. I'd need to play with it.
@sindresorhus I'm happy to tackle this, but I know you have reservations with the idea.
The babel-plugin-espower issue was fixed in #129. Is it different?
Is there still the problem in master?
Yes. Still a problem (when executing ava directly from console - npm test works fine). Also fixed when I upgraded ava to match local version.
@jamestalmage I'm warming up to the idea, but would like to hear some more people's thought about it in xojs/xo#32.
No matter which direction we go, I think it's important we find a way to get rid of the mismatch problems once and for all.