How to Fix: The packages `next` and `create-next-app` have dissappeared

The next and create-next-app packages did not actually vanish from the ecosystem in most cases; this issue is usually caused by a temporary npm registry publishing problem, a registry replication delay, or a local environment resolving package metadata from the wrong source. When npx create-next-app@latest test1 suddenly fails and the package pages appear missing, the root cause is almost always upstream package availability or registry resolution, not your application code.

Understanding the Root Cause

This problem typically happens when the npm package registry temporarily stops serving metadata for one or more packages, or when package pages on npm are briefly unavailable. Since create-next-app is commonly executed through npx, your machine first asks the configured registry for the latest package metadata. If that lookup fails, npx cannot resolve the requested version and the install appears broken.

For the specific symptom where both the package install command and the npm package pages fail at the same time, the strongest indicators are:

• A temporary outage or replication issue on the npm registry.
• An accidental switch to a custom registry in your local .npmrc configuration.
• Cached metadata returning stale or invalid results.
• A short-lived unpublish, deprecate, or visibility issue affecting package metadata delivery.

Because Next.js publishes both next and create-next-app through npm, any disruption in registry metadata can make it look like the packages disappeared entirely, even though the source project still exists.

Step-by-Step Solution

Follow these steps in order to confirm whether the issue is local, registry-related, or already resolved upstream.

1. Verify your npm registry

Make sure your machine is using the official npm registry.

npm config get registry

The expected output is:

https://registry.npmjs.org/

If it points elsewhere, reset it:

npm config set registry https://registry.npmjs.org/

2. Check whether the package metadata is reachable

npm view next version
npm view create-next-app version

If these commands fail with 404, E404, or registry-related errors, the problem is likely external or caused by your current registry configuration.

3. Clear the local npm cache

Corrupted or stale cache entries can cause package resolution issues.

npm cache clean --force

Then try again:

npx create-next-app@latest test1

4. Inspect local and global npm configuration

Look for a project-level or user-level .npmrc overriding the registry.

npm config list

Check for values such as:

• registry=...
• private registry URLs
• proxy settings
• enterprise artifact mirrors

If you are in a company network, a private mirror like Nexus, Verdaccio, or Artifactory may be missing the package or lagging behind public npm replication.

5. Try with an explicit public registry

npx --registry=https://registry.npmjs.org create-next-app@latest test1

This bypasses some misconfigured defaults and is one of the fastest ways to isolate a registry issue.

6. Upgrade Node.js and npm if your toolchain is old

Older versions of Node.js and npm can behave badly with newer package resolution flows.

node -v
npm -v

If needed, update them and rerun the command.

7. Confirm whether npm itself is having problems

If the package pages and CLI requests both fail, check the npm service status and try again after a few minutes. Temporary registry issues often resolve without any code changes.

You can also test package availability directly:

npm view next dist-tags --registry=https://registry.npmjs.org/
npm view create-next-app dist-tags --registry=https://registry.npmjs.org/

8. Use a pinned version as a fallback

If @latest is temporarily problematic, a known published version may still work.

npx create-next-app@15.0.0 test1

Replace the version with one confirmed through npm metadata once the registry is reachable.

Common Edge Cases

• Corporate proxy or private registry mirror: Your company registry may not have synced the latest next metadata yet.
• Incorrect .npmrc in the project directory: A local config file can silently override the global registry.
• Temporary npm website outage but registry still works: The package web page may fail while CLI requests succeed, or the reverse.
• DNS or firewall restrictions: Your network may block access to the npm registry even though general internet access works.
• Cached npx resolution problems: Old cached package data can make npx behave inconsistently until the cache is cleared.
• Typo confusion: The issue title often mentions packages having “disappeared,” but the underlying error may actually be a registry fetch failure, not package removal.

FAQ

Why does npx create-next-app@latest fail even though Next.js still exists on GitHub?

Because npx installs from the npm registry, not directly from GitHub. If npm metadata is unavailable, the command fails even when the source repository is healthy.

How can I tell whether the issue is local or caused by npm?

Run npm view next version and check your configured registry with npm config get registry. If the registry is correct and both package lookups fail, the issue is probably upstream.

Is this caused by my Next.js project code?

No. This failure happens before project scaffolding even starts. It is a package resolution and registry availability problem, not an application bug.

The fastest practical fix is to verify the active registry, clear npm cache, retry using the public registry explicitly, and wait briefly if npm is experiencing a transient outage. In most real-world cases, once registry metadata is restored, create-next-app works again without any changes to your codebase.