-
-
Notifications
You must be signed in to change notification settings - Fork 64
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
Version 2.0.0 is not published in npm #29
Comments
Yep, I haven't got the npm publish access for now. You can use eslint-import-resolver-ts temporarily for now. |
I think I broke my head today trying to apply For now the easiest workaround is to install from the GitHub itself |
@jazzfog The tagged commit is not up to date, I personally do not recommend doing like this. Try |
So why the heck you've created the tag when you actually couldn't publish it and now you even said that it's not up to date? Moreover, the changelog contains only versions that don't exist at all. It's all very confusing. |
Not me. The repository owner is @alexgorbatchev . |
Oh, I see now, my apologies. |
All of the tests are failing for me with the following error:
Any idea what i'm missing? I havent seen this error before. |
@alexgorbatchev Sorry I forgot to add It should have been fixed in 1ffcd83, would you like to try again and publish a new version? |
published, there seem to be an issue with lodash #31 |
There’s a tag v2.0.0, but the corresponding version is not available on npmjs.com.
The text was updated successfully, but these errors were encountered: