Open isaacs opened 9 years ago
Since try-require@1.1.0
is fundamentally broken, this is kind of important. Any users currently depending on ^1.0.0
are getting throws instead of non-throwing require()
s. Please publish 1.2.0 at your earliest availability. Thanks.
I have tried to publish both from work and home. In each case, npmjs.org claims it has published 1.2.0 and now 1.2.1 from home but neither show up via npmjs.org.
Any ideas?
Rich
From: isaacs notifications@github.com<mailto:notifications@github.com> Reply-To: rragan/try-require reply@reply.github.com<mailto:reply@reply.github.com> Date: Thursday, May 21, 2015 at 3:29 PM To: rragan/try-require try-require@noreply.github.com<mailto:try-require@noreply.github.com> Subject: Re: [try-require] npm publish (#6)
Since try-require@1.1.0mailto:try-require@1.1.0 is fundamentally broken, this is kind of important. Any users currently depending on ^1.0.0 are getting throws instead of non-throwing require()s. Please publish 1.2.0 at your earliest availability. Thanks.
— Reply to this email directly or view it on GitHubhttps://github.com/rragan/try-require/issues/6#issuecomment-104440300.
Looks like it finally showed up. Odd.
From: isaacs notifications@github.com<mailto:notifications@github.com> Reply-To: rragan/try-require reply@reply.github.com<mailto:reply@reply.github.com> Date: Thursday, May 21, 2015 at 3:29 PM To: rragan/try-require try-require@noreply.github.com<mailto:try-require@noreply.github.com> Subject: Re: [try-require] npm publish (#6)
Since try-require@1.1.0mailto:try-require@1.1.0 is fundamentally broken, this is kind of important. Any users currently depending on ^1.0.0 are getting throws instead of non-throwing require()s. Please publish 1.2.0 at your earliest availability. Thanks.
— Reply to this email directly or view it on GitHubhttps://github.com/rragan/try-require/issues/6#issuecomment-104440300.
It looks like you've bumped the version number to 1.2.0, but have not published to npm.
If you want to update the version that is delivered via
npm install
, you need to runnpm publish
.(If you're waiting on that for some reason, then feel free to ignore this issue.)