akanix42 / meteor-css-modules

MIT License
92 stars 19 forks source link

"nathantreid:css-modules@3.2.1 : No compatible binary build found for this package" error on 'meteor update' #123

Closed yched closed 5 years ago

yched commented 5 years ago

When running meteor update, I get the following error :

This project is already at Meteor 1.8, the latest release.
=> Errors while upgrading packages:           

While checking for nathantreid:css-modules@3.2.1:
error: No compatible binary build found for this package. Contact the package author and
ask them to publish it for your platform.

I then manually updated nathantreid:css-modules to 3.2.0 instead (meteor add nathantreid:css-modules@3.2.0), but I still get the same error on meteor update, which prevents me from upgrading the other packages.

It seems a 3.2.1 version got somehow published on atmosphere without the associated code ?

akanix42 commented 5 years ago

I'm not sure how that could happen, but I'll look into it.

oswaldoacauan commented 5 years ago

Same error is happening for us. Any news regarding this issue @nathantreid ?

met5678 commented 5 years ago

Having the same issue here.

yched commented 5 years ago

@nathantreid Maybe just issue a new release to get past the buggy thing about 3.2.1 ?

akanix42 commented 5 years ago

I've published 2 releases, nathantreid:css-modules@3.2.2-beta.1 using Meteor 1.7 and nathantreid:css-modules@3.2.2-beta.2 using Meteor 1.8. Please let me know if they work for you - I'm trying to determine if the update to Meteor 1.8 is a breaking change for this package.

yched commented 5 years ago

@nathantreid Thanks !

So, testing with our app (Meteor 1.8):

So it seems republishing new versions fixed meteor update (and will fix it for good when the releases are official, for now it still requires manually updating to the betas to skip 3.2.1). But then something seems broken during compilation with the new versions - and that's what #124 is about.

I should add that our Meteor 1.8 app runs fine with nathantreid:css-modules@3.1.4 so far :-)

akanix42 commented 5 years ago

Thanks for the feedback - I've published 3.2.2 to resolve the issue.