Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

global cli broken if there is any babel version mismatch #157

Closed
jamestalmage opened this issue Nov 8, 2015 · 4 comments
Closed

global cli broken if there is any babel version mismatch #157

jamestalmage opened this issue Nov 8, 2015 · 4 comments
Labels
bug current functionality does not work as desired

Comments

@jamestalmage
Copy link
Contributor

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.
@uiur
Copy link
Contributor

uiur commented Nov 8, 2015

The babel-plugin-espower issue was fixed in #129. Is it different?
Is there still the problem in master?

@jamestalmage
Copy link
Contributor Author

Yes. Still a problem (when executing ava directly from console - npm test works fine). Also fixed when I upgraded ava to match local version.

@sindresorhus
Copy link
Member

@jamestalmage I'm warming up to the idea, but would like to hear some more people's thought about it in xojs/xo#32.

@sindresorhus sindresorhus added the bug current functionality does not work as desired label Nov 8, 2015
@sindresorhus
Copy link
Member

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.

@jamestalmage jamestalmage mentioned this issue Nov 8, 2015
Closed
jamestalmage added a commit to jamestalmage/ava that referenced this issue Nov 27, 2015
@jamestalmage
Prefer the locally installed version of AVA.
81db628 
This hunts for AVA in the locally installed project, and runs that
CLI instead of the globally installed one.

Fixes avajs#157.
@jamestalmage jamestalmage mentioned this issue Nov 27, 2015
Merged
jamestalmage added a commit to jamestalmage/ava that referenced this issue Nov 28, 2015
@jamestalmage
Prefer the locally installed version of AVA.
c62f136 
This hunts for AVA in the locally installed project, and runs that
CLI instead of the globally installed one.

Fixes avajs#157.
jamestalmage added a commit to jamestalmage/ava that referenced this issue Nov 28, 2015
@jamestalmage
Prefer the locally installed version of AVA.
db8d79f 
This hunts for AVA in the locally installed project, and runs that
CLI instead of the globally installed one.

Fixes avajs#157.
jamestalmage added a commit to jamestalmage/ava that referenced this issue Nov 29, 2015
@jamestalmage
Prefer the locally installed version of AVA.
cb58a1a 
This hunts for AVA in the locally installed project, and runs that
CLI instead of the globally installed one.

Fixes avajs#157.
jamestalmage added a commit to jamestalmage/ava that referenced this issue Nov 29, 2015
@jamestalmage
Prefer the locally installed version of AVA.
2f7ac92 
This hunts for AVA in the locally installed project, and runs that
CLI instead of the globally installed one.

Fixes avajs#157.
jamestalmage added a commit that referenced this issue Nov 29, 2015
@jamestalmage
Prefer the locally installed version of AVA.
998ccf2 
This hunts for AVA in the locally installed project, and runs that
CLI instead of the globally installed one.

Fixes #157.
jamestalmage added a commit that referenced this issue Nov 29, 2015
@jamestalmage
Prefer the locally installed version of AVA.
0d82dad 
This hunts for AVA in the locally installed project, and runs that
CLI instead of the globally installed one.

Fixes #157.
This was referenced Sep 12, 2021
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug current functionality does not work as desired
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@uiur @sindresorhus @jamestalmage