-
-
Notifications
You must be signed in to change notification settings - Fork 233
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
Not able to install via npm #81
Comments
same here |
same problem |
+1 |
@eligrey Could you publish to NPM? I spent a lot of time trying to find out why |
@villermen that's what is available for now https://www.npmjs.com/package/eligrey-classlist-js-polyfill |
@englishextra Thanks for the alternative. I understand people picked up the slack but I'd rather not rely on a fork while the main repo still "lives" because forks inevitably lag behind. My solution for now has been to link the latest release directly in our Yarn dependencies, but that excludes us from minor and patch versions. |
@villermen Since I wanted to be consistent I had to do a fork of the version that was tested by that time and it wasn't the latest one. And as I get it right the owners aren't going to do any npm releases. So I live with it. Thanks for your solution. |
npm install only able to get 1.1.20150312 and could not get the latest version.
The text was updated successfully, but these errors were encountered: