next.js: Next 13.5.0 is not pushed to the npm registry

Link to the code that reproduces this issue

https://codesandbox.io/p/sandbox/summer-shape-f7992k?file=/package.json:19,1

To Reproduce

npm i next@13.5.0 or npm i next

Current vs. Expected behavior

Not getting the error:

npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/next/-/next-13.5.0.tgz - Not found
npm ERR! 404
npm ERR! 404  'next@https://registry.npmjs.org/next/-/next-13.5.0.tgz' is not in this registry.
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/xxxxxxxxxxx/.npm/_logs/2023-09-19T16_41_52_628Z-debug-0.log

Verify canary release

I verified that the issue exists in the latest Next.js canary release

Provide environment information

Not relevant

Which area(s) are affected? (Select all that apply)

Package manager (npm, pnpm, Yarn)

Additional context

No response

About this issue

Original URL
State: closed
Created 9 months ago
Reactions: 27
Comments: 36 (7 by maintainers)

Most upvoted comments

From 13.4.19-canary41 to 13.5.0 to 13.5.1-canary1, someone did a whoopsie at vercel

+13

castrosu on Sep 19, 2023

Thanks for opening an issue @hstemplewski.

For commenters, for future reference, “same issue” and similar comments have no value and only add noise and are considered off-topic/spam, not just in this particular issue, but any bug reports. Please use the 👍 upvote on the the issue description in the future, unless you can provide more context about the issue! If you just want to follow the issue, subscribe to notifications instead of adding a comment. Thanks! 🙏

From 13.4.19-canary41 to 13.5.0 to 13.5.1-canary1, someone did a whoopsie at vercel

For the curious, npm had an outage and the stable release was silently failing, halting the release process, so we needed to wait until it was resolved and shipped 13.5.1 as soon as npm was up again. We are sorry for the inconvenience! Happy shipping!

balazsorban44 on Sep 19, 2023

It’s literally in the process of being built and released right now, maybe just hold off for a few minutes 😃 npm especially takes time to propograte:

Even this page flip flops on reload to it showing / not showing. https://www.npmjs.com/package/next?activeTab=versions

Patience people

davecarlson on Sep 19, 2023

Best way is to wait until this is fixed, which shouldn’t take long. But if you need it urgently:

Existing apps: pin Next.js dependencies (next, the eslint package, etc) to 13.4.19
New apps: instead of using create-next-app, clone a known working repository and continue from there, with Next.js version pinned to 13.4.19. This should be one of such working boilerplates: https://vercel.com/templates/next.js/nextjs-boilerplate

joulev on Sep 19, 2023

Why are you trying to install a package that hasn’t been published or released yet ?

Just do a “npx create-next-app @latest” and the error also occurs

i cant do any versions, which ones working?

After you try npx create-next-app@13.14.9 or any other you will get the same error because the step of creation is installing latest version of next 😉

hstemplewski on Sep 19, 2023

I was just about to report this as well. Getting same issue.

techies23 on Sep 19, 2023