Can’t find repo

[ashleynolan]

I’m having some issues when using an old version of postcss-assets (v2.1.3).

Started getting the following error on npm install:

npm ERR! Error: Command failed: Cloning into bare repository '/Users/ashley.nolan/.npm/_git-remotes/git-github.aaakk.us.kg-borodean-image-size-0541338d'...
npm ERR! remote: Repository not found.
npm ERR! fatal: repository 'https://github.com/borodean/image-size/' not found

Is this something that can be fixed? Looks like it’s looking for a fork that no longer exists? (we can’t upgrade to the latest version right now as we’re in process of upgrading our build servers to something that ressembles recent!)

Thanks

[duncanhall]

Also seeing this, seems like it breaks any version prior to the latest.

[borodean]

@ashleynolan @duncanhall sorry for that, I've revived the private fork. However, I'm going to remove it again somewhere this winter when a new release of PostCSS Assets is done — I don't want backwards compatibility to throttle plugin's development.

Also, I should add a note to the README about the versions that could be affected by it.

[borodean]

Okay, I guess I can re-publish older versions of a library with fixed dependencies. Will do that later, for now it should be fine with the revived fork.

[borodean]

@ashleynolan @duncanhall I've published a patched 2.1.x under version 2.1.4 where the private fork is no longer used.

In conclusion, releases 2.1.0—3.0.2 would no longer work without that private fork existing. But now for the 3.0.x versions there is 3.0.3 fixing this thing, and for 2.1.x there is 2.1.4 doing so.

Since there are solutions for every minor version now, I'll remove the fork again.

Sorry for the inconvenience and thanks for reporting.

[ashleynolan]

@borodean thanks for the fix – all working as expected now 👍

[hudochenkov]

@borodean this republish bring new issue: npm install postcss-assets installs 2.1.4 instead of 3.0.3 and PostCSS 5 is very unhappy with this :)

[borodean]

@hudochenkov crappy crap. That happened because I've published 2.1.4 after 3.0.3.

Hmm, I wonder how this could be fixed.

[hudochenkov]

@borodean maybe publish 3.0.3 again, or bump to 3.0.4 and publish.

[borodean]

This command fixed the issue:

npm dist-tag add [email protected] latest

So 3.0.3 is marked as the latest one again, and npm i postcss-assets would pick it.

Thanks for reporting, @hudochenkov!

[hudochenkov]

@borodean thank you for quick fixing :)