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

on npm version 2.0 is available instead of 2.2 #73

Closed
sagarkaurav opened this issue Sep 3, 2017 · 9 comments
Closed

on npm version 2.0 is available instead of 2.2 #73

sagarkaurav opened this issue Sep 3, 2017 · 9 comments

Comments

@sagarkaurav
Copy link

sagarkaurav commented Sep 3, 2017

@oligibson new version is not published on npm. Please update it.

@jessamarie
Copy link

@sagarkaurav

Try npm install --save devicon-2.2. It works for me!

@sagarkaurav
Copy link
Author

@jessamarie I am using yarn and yarn add devicon@2.2 doesn't seems to work!.

@jessamarie
Copy link

jessamarie commented Sep 5, 2017

@sagarkaurav For some reason you have to use a different package name, but it should work with yarn as well. Use this command instead: yarn add devicon-2.2

@sagarkaurav
Copy link
Author

@jessamarie thanks its worked but i am still curious why different name is used and why is devicon 2.2 is not available?

@fpoumian
Copy link

I had the same issue when I tried upgrading from version 2.0 to 2.2 on Yarn (I solved it by removing the original package and installing that separate 2.2 package). Will all future releases be released in separate packages in Yarn?

@adamski52
Copy link

since 2.2, it's a package named devicon-2.2 with a version of 2.2.0. whoever owns the original devicon packages needs to npm publish please.

putting the version number in the package name is bad joojoo: npm install devicon-2-2@2.2.0 will work. npm install devicon@2.2.0 will not.

@baer
Copy link

baer commented Dec 11, 2017

To add to @adamski52's comment:

  • devicon-2.2 is a different package published by boomhq
  • That package is NOT owned by @konpa

@konpa would it be possible to publish the latest to NPM?

@dougmaitelli
Copy link

Sorry guys, but it looks to me that this repository is not being maintained anymore. Also, if we keep adding icons in a font file it will become too large for projects to use.

I would suggest migrating to: https://github.com/gilbarbara/logos/ and use the SVG files independently.

@iamclaytonray
Copy link
Contributor

Hey, we are working on getting back on track. We will be following SEMVER releases from now on! I'll go ahead and close this issue. (Docs will be updated accordingly in the future. Trying to get the website back up at the moment.)

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

7 participants