8000 `create-next-app@latest` install the Next.js template at version 15.1.8 instead of the latest template version · Issue #79532 · vercel/next.js · GitHub
[go: up one dir, main page]
Skip to content

create-next-app@latest install the Next.js template at version 15.1.8 instead of the latest template version #79532

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
congthanh1910 opened this issue May 23, 2025 · 9 comments
Closed

create-next-app@latest install the Next.js template at version 15.1.8 instead of the latest template version #79532

congthanh1910 opened this issue May 23, 2025 · 9 comments
Labels
create-next-app Related to our CLI tool for quickly starting a new Next.js application.

Comments

@congthanh1910
Copy link
congthanh1910 commented May 23, 2025 •
edited
Loading

Link to the code that reproduces this issue

https://github.com/congthanh1910/test-create-latest-version

To Reproduce

It can be seen in the repository above, the version generated is v15.1.8

Image

Current vs. Expected behavior

Current: use v15.1.8 template
Expected: use latest template version

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
Binaries:
  Node: 22.16.0
  npm: 10.9.2
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 15.1.8 // Latest available version is detected (15.1.8).
  eslint-config-next: 15.1.8
  react: 19.1.0
  react-dom: 19.1.0
  typescript: 5.8.3
Next.js Config:
  output: N/A

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

create-next-app

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

next dev (local), next build (local), next start (local)

Additional context

No response
@github-actions github-actions bot added the create-next-app Related to our CLI tool for quickly starting a new Next.js application. label May 23, 2025
@congthanh1910 congthanh1910 changed the title create-next-app@latest install next@15.1.8 instead of latest version create-next-app@latest install the Next.js template at version 15.1.8 instead of the latest template version May 23, 2025
@bytesizedwizard
Copy link

I think the latest tag has been mistakenly tagged to v15.1.8.

Can confirm this on npm as well, I think this was the relevant build that caused the issue -

https://github.com/vercel/next.js/actions/runs/15196217215/attempts/1

@icyJoseph
Copy link
Contributor

Hi,

We released 15.1.8 which is backporting some bug fixes. And yeah, the latest tag has to be fixed. We are looking into it. Thanks for reporting.

@shawnchan99
Copy link
shawnchan99 commented May 23, 2025 •
edited
Loading

And its default verion of Tailwindcss is set to 3.4.1 instead of 4.1 during the npx create-next-app@latest CLI. No previous warning. No explanation afterward. Could anyone help to confirm my finding?

@chrisweb
Copy link
Contributor
chrisweb commented May 23, 2025 •
edited
Loading

EDIT: my comment is now obsolete as this got fixed, you can again use npx create-next-app or npx create-next-app@latest

In the meantime as a work around, when using create next app pin the exact version, using the command like this:

npx create-next-app@15.3.2 . --typescript --tailwind --eslint --app --turbopack --import-alias "@/*" --use-npm --no-src-dir

Adjust the options to your liking or leave them away i 8000 f you prefer answering the questions

@ducviet1696
Copy link

It might be a mistake in tagging the release. I see that they have been backporting bug fixes to the previous versions

@icyJoseph
Copy link
Contributor

Hi, this got fixed over the weekend. Thanks you all for your input.

@szhsin
Copy link
szhsin commented May 27, 2025

@icyJoseph the latest dist-tag of eslint-config-next is incorrectly pointing to a canary version instead of a stable release, see #79605

@icyJoseph
Copy link
Contributor

@szhsin thanks for the input, I'll see what's up with that. I noticed that the bundle analyzer package is also doing that.

@icyJoseph
Copy link
Contributor

@szhsin both packages, eslint-config-next, @next/bundle-analyzer are not pointing to the correct version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
create-next-app Related to our CLI tool for quickly starting a new Next.js application.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@chrisweb @icyJoseph @ducviet1696 @szhsin @shawnchan99 @bytesizedwizard @congthanh1910
0