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.

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

warn Unable to resolve version 2.2.0 for ansi-styles #19

Closed
ryanmcdonough opened this issue Apr 1, 2016 · 13 comments
Closed

warn Unable to resolve version 2.2.0 for ansi-styles #19

ryanmcdonough opened this issue Apr 1, 2016 · 13 comments

Comments

@ryanmcdonough
Copy link

I've looked at the issue that relates to 2.2.0 being unpublished, I've ran NPM shrinkwrap and change items to 2.2.1 - however I'm still getting:

warn Unable to resolve version 2.2.0 for ansi-styles

appearing multiple times during jspm install causing the entire thing to fail.

Am I missing something here?

error.txt

npm-shrinkwrap.txt

@Qix-
Copy link
Member

Qix- commented Apr 1, 2016

Does this help at all?

@Qix- Qix- closed this as completed Apr 1, 2016
@ryanmcdonough
Copy link
Author

@Qix- Sadly not, it's on a build server this is happening so the environment is trashed everytime so it's a fresh jspm each time.

@Qix- Qix- reopened this Apr 1, 2016
@Qix-
Copy link
Member

Qix- commented Apr 1, 2016

Can you bump Chalk to version 1.1.3? This shouldn't be happening, your npm-shrinkwrap.txt looks fine.

It could be that the CI you're using is caching modules or something, or it's behind a private registry. Versions should be fixed now, so anything like this is generally a caching problem of some sort.

@patrickmichalina
Copy link

What is going on with this? I am getting the same error.

@Qix-
Copy link
Member

Qix- commented Apr 4, 2016

@patrickmichalina Have you tried everything listed above? If so, I'm pretty sure it's a bug with jspm.

@patrickmichalina
Copy link

@Qix- Yes, I have tried clearing both npm and jspm caches. Neither resolves the issue directly. With JSPM I think the real fix is to delete the entire "map" object in the config.js file (sometimes named jspm.config.js). After that do a jspm cache-clear and should fix it right up.

@Qix-
Copy link
Member

Qix- commented Apr 4, 2016

@patrickmichalina can you confirm that worked? (I've never used jspm)

// @sindresorhus have you used jspm?

@patrickmichalina
Copy link

Yes sorry. It worked. I used that method to fix my project.

@Qix-
Copy link
Member

Qix- commented Apr 4, 2016

@ryanmcdonough can you try @patrickmichalina's solution and see if it works for you? Not sure if this something that is done in the project itself or if the CI will need to be fixed.

@patrickmichalina
Copy link

@ryanmcdonough @Qix- Since this file is stored in source control, this fix works in CI. I can confirm. Deployed with VSTS online using this fix.

@Qix-
Copy link
Member

Qix- commented Apr 4, 2016

Great! I'm going to go ahead and close this.

@ryanmcdonough if this doesn't end up working for you, let me know. 👍

Thanks for the help @patrickmichalina!

@Qix- Qix- closed this as completed Apr 4, 2016
@ryanmcdonough
Copy link
Author

@Qix- @patrickmichalina that worked perfectly. Well in my case I upaed the maps in the config to 1.1.3 rather than cleared them and it worked.

@Qix-
Copy link
Member

Qix- commented Apr 4, 2016

Glad to hear it! Thanks again for all the help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants