Closed jcolemorrison closed 9 years ago
Ah yes. It's strange that Meteor decides to publish one's local NPM registry settings. I'll have to figure out how to tell Meteor not to. Thanks for the heads up!
Also encountering this error when deploying my app to modulus.
Yeah, if you switch back to the 1.5.6 version it all seems to work fine.
On Fri, Feb 13, 2015 at 11:22 AM, Josh notifications@github.com wrote:
Also encountering this error when deploying my app to modulus.
— Reply to this email directly or view it on GitHub https://github.com/tyler-johnson/stripe-meteor/issues/28#issuecomment-74310612 .
As a workaround I went ahead and cloned the repository and made the package a local meteor package for my project, in the end this isn't ideal but it gets me back up and running with the latest version.
Alright, this should be fixed with v2.1.0. I have also pushed the .npm/packages
folder as suggested by Meteor, which should clear up future problems.
Currently, trying to npm install the package or the tar.gz results in a "forbidden" error:
https://registry.beneaththeink.com/stripe/-/stripe-3.1.0.tgz
Just navigating to that link will tell you what I mean.
Looks like a simple misstep in the npm settings.