vercel-release-bot
7d8fab2f4d
v14.0.4-canary.35
2023-12-01 23:22:14 +00:00
vercel-release-bot
574e7060b1
v14.0.4-canary.34
2023-12-01 20:52:57 +00:00
vercel-release-bot
d71d7767f3
v14.0.4-canary.33
2023-12-01 16:19:08 +00:00
vercel-release-bot
fa9cd3efc4
v14.0.4-canary.32
2023-12-01 04:31:03 +00:00
vercel-release-bot
1b08dfe040
v14.0.4-canary.31
2023-11-30 23:22:21 +00:00
vercel-release-bot
3159fa197b
v14.0.4-canary.30
2023-11-30 23:10:37 +00:00
vercel-release-bot
73d4ca5775
v14.0.4-canary.29
2023-11-30 22:56:34 +00:00
vercel-release-bot
54544c9019
v14.0.4-canary.28
2023-11-29 23:22:05 +00:00
vercel-release-bot
0345ee85f8
v14.0.4-canary.27
2023-11-29 20:00:26 +00:00
vercel-release-bot
cec374f98c
v14.0.4-canary.26
2023-11-29 18:34:18 +00:00
vercel-release-bot
e1a2b12bee
v14.0.4-canary.25
2023-11-28 23:22:30 +00:00
vercel-release-bot
266fc8e318
v14.0.4-canary.24
2023-11-28 23:04:45 +00:00
vercel-release-bot
6ac1367687
v14.0.4-canary.23
2023-11-28 22:24:13 +00:00
vercel-release-bot
d0c5673d37
v14.0.4-canary.22
2023-11-28 18:26:06 +00:00
vercel-release-bot
6fd3c3b992
v14.0.4-canary.21
2023-11-28 17:00:46 +00:00
vercel-release-bot
113a125a93
v14.0.4-canary.20
2023-11-28 16:44:35 +00:00
vercel-release-bot
7ff3e3e32d
v14.0.4-canary.19
2023-11-27 23:22:35 +00:00
vercel-release-bot
7874ad2659
v14.0.4-canary.18
2023-11-26 23:21:26 +00:00
vercel-release-bot
12a683b925
v14.0.4-canary.17
2023-11-25 23:21:36 +00:00
vercel-release-bot
f6070c807b
v14.0.4-canary.16
2023-11-24 23:21:37 +00:00
vercel-release-bot
1496d50f68
v14.0.4-canary.15
2023-11-24 19:37:49 +00:00
vercel-release-bot
b27a3525c7
v14.0.4-canary.14
2023-11-24 13:41:03 +00:00
vercel-release-bot
6bfd1458b2
v14.0.4-canary.13
2023-11-23 23:22:46 +00:00
vercel-release-bot
936becb8b6
v14.0.4-canary.12
2023-11-23 15:15:06 +00:00
vercel-release-bot
0155ec70d7
v14.0.4-canary.11
2023-11-22 23:22:02 +00:00
vercel-release-bot
8f9e494cb5
v14.0.4-canary.10
2023-11-22 12:48:53 +00:00
vercel-release-bot
c0bafcb354
v14.0.4-canary.9
2023-11-22 02:11:25 +00:00
vercel-release-bot
f6b50ae32b
v14.0.4-canary.8
2023-11-21 23:22:46 +00:00
vercel-release-bot
8b11264ea9
v14.0.4-canary.7
2023-11-21 19:04:07 +00:00
vercel-release-bot
0a4f26f1ef
v14.0.4-canary.6
2023-11-20 23:22:25 +00:00
vercel-release-bot
32c9ce6805
v14.0.4-canary.5
2023-11-19 23:21:38 +00:00
vercel-release-bot
43b075eb7e
v14.0.4-canary.4
2023-11-18 23:21:24 +00:00
vercel-release-bot
c0e5d6584d
v14.0.4-canary.3
2023-11-17 23:22:09 +00:00
vercel-release-bot
6984ac4b86
v14.0.4-canary.2
2023-11-17 15:05:24 +00:00
vercel-release-bot
82beef92a4
v14.0.4-canary.1
2023-11-16 23:22:02 +00:00
vercel-release-bot
1ae13b5d9f
v14.0.4-canary.0
2023-11-16 21:40:51 +00:00
vercel-release-bot
391471b315
v14.0.3
2023-11-16 18:37:33 +00:00
vercel-release-bot
32875e4fe4
v14.0.3-canary.12
2023-11-16 16:00:52 +00:00
vercel-release-bot
c8bfda4367
v14.0.3-canary.11
2023-11-15 23:22:09 +00:00
vercel-release-bot
a5515693bc
v14.0.3-canary.10
2023-11-15 21:51:36 +00:00
vercel-release-bot
7281cd3fc4
v14.0.3-canary.9
2023-11-15 13:00:05 +00:00
vercel-release-bot
44613dc045
v14.0.3-canary.8
2023-11-14 23:23:29 +00:00
vercel-release-bot
08e5424ddc
v14.0.3-canary.7
2023-11-14 10:25:41 +00:00
vercel-release-bot
82821c7942
v14.0.3-canary.6
2023-11-13 23:22:10 +00:00
vercel-release-bot
d7ade76ef8
v14.0.3-canary.5
2023-11-12 23:22:46 +00:00
vercel-release-bot
a794e1f32e
v14.0.3-canary.4
2023-11-12 08:17:33 +00:00
vercel-release-bot
00f5b5e789
v14.0.3-canary.3
2023-11-11 23:23:28 +00:00
vercel-release-bot
c74f023b88
v14.0.3-canary.2
2023-11-10 23:21:25 +00:00
vercel-release-bot
7966eaf0f2
v14.0.3-canary.1
2023-11-10 04:31:01 +00:00
vercel-release-bot
52123ccdbc
v14.0.3-canary.0
2023-11-09 23:22:17 +00:00
vercel-release-bot
8eba72f30b
v14.0.2
2023-11-09 18:32:59 +00:00
vercel-release-bot
fdd6eb990a
v14.0.2-canary.27
2023-11-09 17:45:04 +00:00
vercel-release-bot
b740fe8fa4
v14.0.2-canary.26
2023-11-09 09:56:42 +00:00
vercel-release-bot
fd7ea115b5
v14.0.2-canary.25
2023-11-09 02:36:39 +00:00
vercel-release-bot
b50090bf96
v14.0.2-canary.24
2023-11-08 23:21:44 +00:00
vercel-release-bot
67656c3fec
v14.0.2-canary.23
2023-11-08 20:21:15 +00:00
vercel-release-bot
5dc2572dc7
v14.0.2-canary.22
2023-11-08 16:23:23 +00:00
vercel-release-bot
f206573f93
v14.0.2-canary.21
2023-11-08 10:25:06 +00:00
vercel-release-bot
3977f90fd0
v14.0.2-canary.20
2023-11-08 02:39:50 +00:00
vercel-release-bot
0697be3b57
v14.0.2-canary.19
2023-11-07 23:24:29 +00:00
vercel-release-bot
ded28edeae
v14.0.2-canary.18
2023-11-07 04:46:46 +00:00
vercel-release-bot
d95900c7b0
v14.0.2-canary.17
2023-11-07 00:44:19 +00:00
vercel-release-bot
3eaa96fff6
v14.0.2-canary.16
2023-11-06 23:21:39 +00:00
vercel-release-bot
c29c039cf3
v14.0.2-canary.15
2023-11-06 20:56:03 +00:00
vercel-release-bot
38e8b523dc
v14.0.2-canary.14
2023-11-06 17:08:35 +00:00
vercel-release-bot
31c2f976cd
v14.0.2-canary.13
2023-11-05 23:23:20 +00:00
vercel-release-bot
8536ad98dd
v14.0.2-canary.12
2023-11-04 23:21:06 +00:00
vercel-release-bot
d0ac7c2f45
v14.0.2-canary.11
2023-11-03 23:22:55 +00:00
vercel-release-bot
ffdfd33251
v14.0.2-canary.10
2023-11-03 12:13:32 +00:00
vercel-release-bot
8014866cac
v14.0.2-canary.9
2023-11-02 23:21:41 +00:00
vercel-release-bot
f979341f82
v14.0.2-canary.8
2023-11-02 20:34:16 +00:00
vercel-release-bot
ad55d78199
v14.0.2-canary.7
2023-11-02 19:59:43 +00:00
vercel-release-bot
1c5d7782a0
v14.0.2-canary.6
2023-11-01 23:21:29 +00:00
vercel-release-bot
b0509ed53a
v14.0.2-canary.5
2023-11-01 13:30:21 +00:00
vercel-release-bot
0f98dccff7
v14.0.2-canary.4
2023-11-01 13:02:40 +00:00
vercel-release-bot
c0baa0ac23
v14.0.2-canary.3
2023-11-01 02:30:21 +00:00
vercel-release-bot
e0cf4e2ebd
v14.0.2-canary.2
2023-10-31 23:22:41 +00:00
vercel-release-bot
033ba46f56
v14.0.2-canary.1
2023-10-31 09:34:35 +00:00
Nhan Doan
adc636dd54
fix: update Next.js version in create-next-app ( #57532 )
...
### What?
The default template generated from `create-next-app` still says **Next.js 13**.
<img width="1053" alt="image" src="https://github.com/vercel/next.js/assets/2561973/1413dcda-d73d-43a9-ba47-8322cf193c52 ">
### Why?
Next.js 14 is released.
2023-10-31 01:36:27 +00:00
vercel-release-bot
5eb6607279
v14.0.2-canary.0
2023-10-30 23:23:45 +00:00
vercel-release-bot
4df888a55f
v14.0.1
2023-10-30 19:21:25 +00:00
vercel-release-bot
41dec2cbd6
v14.0.1-canary.5
2023-10-30 18:37:29 +00:00
moka-ayumu
0623a4f79f
Modify tailwindcss related dependency of create-next-app ( #57262 )
...
### What?
If the version of `autoprefixer` is 10.0.0 and the version of `tailwindcss` is less than 3.3.0, the error `RangeError: Maximum call stack size exceeded` occurs when you create with tailwindcss & typescript and run it.
### Why?
The exact reason is unknown, but it appears to be a compatibility issue. Also, currently configuring tailwindcss with ts makes the tailwind config file in ts, which is supported since tailwindcss version 3.3.0. (In js, it works even if you set the version of `autoprefixer` to 10.0.1 and lower the version of tailwindcss.)
### How?
Simply default the minimum version of `autoprefixer` to 10.0.1 and the minimum version of `tailwindcss` to 3.3.0.
2023-10-30 17:54:28 +00:00
vercel-release-bot
9d49afc5ea
v14.0.1-canary.4
2023-10-30 17:29:15 +00:00
vercel-release-bot
fc1ecc407c
v14.0.1-canary.3
2023-10-29 23:22:02 +00:00
vercel-release-bot
54a9da0a1e
v14.0.1-canary.2
2023-10-28 23:21:43 +00:00
vercel-release-bot
c70506de77
v14.0.1-canary.1
2023-10-27 23:22:34 +00:00
vercel-release-bot
6a63c4ffeb
v14.0.1-canary.0
2023-10-26 23:22:39 +00:00
vercel-release-bot
b546d8b22c
v14.0.0
2023-10-26 16:04:54 +00:00
vercel-release-bot
356dc42f1a
v13.5.7-canary.37
2023-10-26 12:34:50 +00:00
vercel-release-bot
fc1b6c4742
v13.5.7-canary.36
2023-10-26 11:42:38 +00:00
vercel-release-bot
c7d02f48b2
v13.5.7-canary.35
2023-10-26 08:44:45 +00:00
vercel-release-bot
a9fc27a8e5
v13.5.7-canary.34
2023-10-26 07:19:26 +00:00
vercel-release-bot
abb34da8bd
v13.5.7-canary.33
2023-10-26 06:19:34 +00:00
vercel-release-bot
0127fc75a1
v13.5.7-canary.32
2023-10-26 05:27:36 +00:00
vercel-release-bot
18d797e3fd
v13.5.7-canary.31
2023-10-26 04:47:54 +00:00
vercel-release-bot
668820100a
v13.5.7-canary.30
2023-10-26 03:34:50 +00:00
vercel-release-bot
b27aa57908
v13.5.7-canary.29
2023-10-26 01:57:13 +00:00
vercel-release-bot
1df027f46e
v13.5.7-canary.28
2023-10-26 01:01:59 +00:00
vercel-release-bot
7274296681
v13.5.7-canary.27
2023-10-25 20:35:14 +00:00
vercel-release-bot
2b400f8fc3
v13.5.7-canary.26
2023-10-25 20:06:39 +00:00
vercel-release-bot
1d8764cd1b
v13.5.7-canary.25
2023-10-24 23:22:49 +00:00
vercel-release-bot
2b2ad9c7c4
v13.5.7-canary.24
2023-10-24 22:05:40 +00:00
vercel-release-bot
2fc2a52652
v13.5.7-canary.23
2023-10-24 08:22:51 +00:00
vercel-release-bot
c77fec827f
v13.5.7-canary.22
2023-10-24 05:34:15 +00:00
vercel-release-bot
96337342e4
v13.5.7-canary.21
2023-10-24 03:58:21 +00:00
vercel-release-bot
dc7b5d806e
v13.5.7-canary.20
2023-10-24 00:35:28 +00:00
vercel-release-bot
7c803a762e
v13.5.7-canary.19
2023-10-23 23:24:21 +00:00
vercel-release-bot
8fb5c8517f
v13.5.7-canary.18
2023-10-23 22:17:01 +00:00
vercel-release-bot
799e6ca65a
v13.5.7-canary.17
2023-10-23 18:13:11 +00:00
vercel-release-bot
dc88b413f8
v13.5.7-canary.16
2023-10-23 03:07:00 +00:00
vercel-release-bot
2762511796
v13.5.7-canary.15
2023-10-22 23:22:41 +00:00
vercel-release-bot
e5c082418d
v13.5.7-canary.14
2023-10-21 23:23:17 +00:00
vercel-release-bot
d0a1199a36
v13.5.7-canary.13
2023-10-20 23:23:41 +00:00
vercel-release-bot
2b60475c2b
v13.5.7-canary.12
2023-10-20 17:19:41 +00:00
vercel-release-bot
e437f72662
v13.5.7-canary.11
2023-10-19 23:22:57 +00:00
vercel-release-bot
143d79f733
v13.5.7-canary.10
2023-10-19 22:41:38 +00:00
vercel-release-bot
ed6b60c55a
v13.5.7-canary.9
2023-10-19 19:15:58 +00:00
Jiachi Liu
a6aae865c4
Bump packages version to match canary versions ( #57071 )
...
We released 13.5.6 as stable patch, need to bump the canary version
higher than stable to match the semantics
2023-10-19 12:09:06 -07:00
vercel-release-bot
dc7bc70d4d
v13.5.6-canary.8
2023-10-19 16:49:59 +00:00
JJ Kasper
3010ae10e1
Update CNA tests to avoid publish conflict ( #57025 )
...
This avoids testing against latest exact canary version as this causes these tests to fail while the publish is still in progress. As a follow-up we can investigate moving this post publish or packing/deploying tarballs to use.
Co-authored-by: Steven <229881+styfle@users.noreply.github.com>
2023-10-19 13:52:10 +00:00
vercel-release-bot
4c2b34ea7c
v13.5.6-canary.7
2023-10-18 23:24:25 +00:00
leung018
66597be8a7
Add .yarn/install-state.gz to .gitignore ( #56637 )
...
### Reason for making this change
https://yarnpkg.com/getting-started/qa#:~:text=yarn%2Finstall%2Dstate.,your%20workspaces%20all%20over%20again .
In the official documentation of `yarn`, it is stated that `.yarn/install-state.gz` is an optimization file that developer shouldn't ever have to commit. However, currently, when running `create-next-app`, `.yarn/install-state.gz` is being commited.
### Remaining work
I apologize for only modifying one template initially to initiate the discussion first.
If this change is agreed upon, it should be synchronized with other `.gitignore` templates. Would it be possible to follow a similar approach as in https://github.com/vercel/next.js/pull/47241 ? I would appreciate any assistance in syncing this change.
2023-10-18 16:34:48 +00:00
vercel-release-bot
2c8606e596
v13.5.6-canary.6
2023-10-18 06:59:43 +00:00
vercel-release-bot
318cbbf9b1
v13.5.6-canary.5
2023-10-17 23:22:33 +00:00
vercel-release-bot
f19dabbc6d
v13.5.6-canary.4
2023-10-17 21:22:19 +00:00
Balázs Orbán
523474c8be
chore: lower Node.js version requirement ( #56943 )
2023-10-17 23:15:31 +02:00
vercel-release-bot
df1d4a16aa
v13.5.6-canary.3
2023-10-17 16:36:35 +00:00
vercel-release-bot
ee9bee96af
v13.5.6-canary.2
2023-10-17 13:26:58 +00:00
vercel-release-bot
24a146680f
v13.5.6-canary.1
2023-10-16 23:24:30 +00:00
vercel-release-bot
3c7d15b992
v13.5.6-canary.0
2023-10-16 22:04:56 +00:00
Balázs Orbán
1ff7f07875
feat: drop Node.js 16 ( #56896 )
...
### What?
BREAKING CHANGE: Bump the minimum required Node.js version.
### Why?
Node.js 16 has reached end-of-life in September.
Bumped to `18.18.2` since it contained some security-related patches: https://nodejs.org/en/blog/vulnerability/october-2023-security-releases
### How?
Bumped `engines` where needed, upgraded the workflows.
This will allow us to remove quite a few polyfills, I'll open separate PRs for those.
2023-10-16 21:41:38 +00:00
vercel-release-bot
54145b49f9
v13.5.5
2023-10-16 14:54:10 +00:00
vercel-release-bot
1609da2d95
v13.5.5-canary.19
2023-10-16 13:44:03 +00:00
vercel-release-bot
c1c419fde0
v13.5.5-canary.18
2023-10-16 12:28:32 +00:00
vercel-release-bot
e5ad069c6a
v13.5.5-canary.17
2023-10-15 23:22:55 +00:00
vercel-release-bot
297efa7bc9
v13.5.5-canary.16
2023-10-14 23:22:14 +00:00
vercel-release-bot
46d56c6bca
v13.5.5-canary.15
2023-10-13 23:22:28 +00:00
vercel-release-bot
f3973d84a5
v13.5.5-canary.14
2023-10-13 22:44:36 +00:00
vercel-release-bot
f95a11f804
v13.5.5-canary.13
2023-10-13 16:34:44 +00:00
vercel-release-bot
489a528003
v13.5.5-canary.12
2023-10-13 13:23:54 +00:00
vercel-release-bot
e0cd06531b
v13.5.5-canary.11
2023-10-12 23:23:04 +00:00
vercel-release-bot
f306108b37
v13.5.5-canary.10
2023-10-12 23:09:37 +00:00
Hamir Mahal
9288ef4921
feat: add self-documenting .env.example file ( #56469 )
...
- fixes #56468
Co-authored-by: Steven <229881+styfle@users.noreply.github.com>
2023-10-12 21:55:14 +00:00
vercel-release-bot
8013ef7372
v13.5.5-canary.9
2023-10-12 17:27:01 +00:00
vercel-release-bot
7d8cf1f9f3
v13.5.5-canary.8
2023-10-12 00:58:02 +00:00
vercel-release-bot
ec0a8dac03
v13.5.5-canary.7
2023-10-11 13:05:55 +00:00
vercel-release-bot
e8048b9974
v13.5.5-canary.6
2023-10-11 04:25:10 +00:00
vercel-release-bot
1b7895e0a4
v13.5.5-canary.5
2023-10-10 16:04:34 +00:00
Zack Tanner
e039cc72fc
enable verbatimModuleSyntax to make type imports/exports explicit ( #56551 )
...
This has come up in code review a few times, so enabling the tsconfig setting so it's more easily caught.
2023-10-07 15:09:54 +00:00
vercel-release-bot
78b91243dd
v13.5.5-canary.4
2023-10-06 15:46:54 +00:00
vercel-release-bot
5aca71cfa6
v13.5.5-canary.3
2023-10-06 12:00:47 +00:00
Hamir Mahal
187df91438
fix: .../templates/*/app/layout.* import order ( #56380 )
...
- fixes #56379
2023-10-04 20:41:47 +00:00
vercel-release-bot
400c679791
v13.5.5-canary.2
2023-10-04 19:01:01 +00:00
vercel-release-bot
28767ad96a
v13.5.5-canary.1
2023-10-04 13:17:50 +00:00
vercel-release-bot
e34fdf2890
v13.5.5-canary.0
2023-10-03 21:23:02 +00:00
vercel-release-bot
1e8dca4a87
v13.5.4
2023-10-03 01:40:53 +00:00
vercel-release-bot
9e24d6ff3b
v13.5.4-canary.11
2023-10-03 00:36:26 +00:00
vercel-release-bot
db48052a5e
v13.5.4-canary.10
2023-10-02 23:23:48 +00:00
vercel-release-bot
033e8a5c87
v13.5.4-canary.9
2023-10-02 09:02:04 +00:00
vercel-release-bot
489f7fda4b
v13.5.4-canary.8
2023-09-29 22:28:11 +00:00
vercel-release-bot
af3205637d
v13.5.4-canary.7
2023-09-29 12:10:52 +00:00
Balázs Orbán
4ec443931a
fix(cna): pin dependency versions ( #56177 )
...
### What?
This PR is pinning the installed versions of dependencies in `create-next-app`
### Why?
Currently, we write `latest` to `package.json`,
### How?
As far as I can tell, there is no way to update the `package.json` file based on the lockfile (which does have the information needed).
Major versions are bumped less frequently, so this should be fine to update manually.
Other alternatives would be:
- return to the previous way of running `npm i --save` and `npm i --save-dev` instead (ref: #55730 ). This might be slightly slower than one `npm i` pass though.
- fetch the latest versions of each package from the registry. Might be even slower
NOTE: The user has always the alternative to update the versions to their desired ones afterward.
Fixes #56174
2023-09-28 18:22:02 +00:00
vercel-release-bot
e18c9dde3f
v13.5.4-canary.6
2023-09-28 15:00:44 +00:00
vercel-release-bot
49f646da14
v13.5.4-canary.5
2023-09-28 13:48:17 +00:00
vercel-release-bot
f5ac079e54
v13.5.4-canary.4
2023-09-27 23:17:38 +00:00
vercel-release-bot
2ff2c0b4b2
v13.5.4-canary.3
2023-09-27 21:43:46 +00:00
vercel-release-bot
778a3c55cf
v13.5.4-canary.2
2023-09-27 17:29:49 +00:00
Vũ Văn Dũng
cf3d73a46b
Add the default import alias to create-next-app prompt for clarity ( #55896 )
...
### Why?
Whenever I run `create-next-app` and reach this question
```
Would you like to customize the default import alias? No / Yes
```
I always have to select "No", because I don't remember what this default import alias here is. [It _is_ documented to be `@/*`](https://nextjs.org/docs/app/api-reference/create-next-app#non-interactive ), but the documentation is relatively hidden and not many people know about it – it's also easy to forget.
Even more confusingly, the next question ("What import alias would you like configured?") doesn't have this `@/*` as the default answer, but the user's last choice as the default answer instead (which could be different from `@/*` – making people wonder if Next.js changed their defaults overnight).
I suppose it would be better to just make it clear in the prompt itself, so people with skill issues who happen to forget that default value (like me) can still confidently select "Yes" if they want `@/*`, without having to do "No" and manually type `@/*` again.
### How
```diff
- Would you like to customize the default import alias?
+ Would you like to customize the default import alias (@/*)?
```
2023-09-26 22:58:46 +00:00
vercel-release-bot
e3a2805151
v13.5.4-canary.1
2023-09-26 13:31:19 +00:00
vercel-release-bot
df3980da88
v13.5.4-canary.0
2023-09-25 21:03:03 +00:00
Balázs Orbán
37b5cea794
chore: NextJS -> Next.js ( #55961 )
2023-09-25 14:53:11 +00:00
vercel-release-bot
76e06d55a8
v13.5.3
2023-09-25 14:24:47 +00:00
vercel-release-bot
b98ebb2806
v13.5.3-canary.4
2023-09-25 13:16:18 +00:00
vercel-release-bot
ec671bb5f5
v13.5.3-canary.3
2023-09-23 02:02:57 +00:00
vercel-release-bot
c923257c1b
v13.5.3-canary.2
2023-09-22 19:42:08 +00:00
vercel-release-bot
0d6f3ac36b
v13.5.3-canary.1
2023-09-21 23:58:45 +00:00
Balázs Orbán
bca6ff77f9
fix(cna): separate dependencies/devDependencies ( #55730 )
...
### What?
As [discussed](https://vercel.slack.com/archives/C04DUD7EB1B/p1692183798097169 ), we should follow the ecosystem standard separation of dependencies and dev dependencies.
### Why?
This is a common issue/misunderstanding that we always have to explain separately, while there is no real benefit.
One counter-argument was that install times would be increased when we had to run install for `dependencies` and `devDependencies` separately, but that's easy to work around as explained below.
### How?
Instead of passing the `dependencies` array to the package manager in the CLI, we write these to the `package.json` file and then run the package manager's install command without the dependency arguments.
This will also reduce the number of writes to the `package.json` file from two to just one.
Ref: https://github.com/vercel/next.js/pull/42218 , https://github.com/vercel/next.js/pull/48076 , https://github.com/vercel/next.js/issues/54105 , https://github.com/vercel/next.js/pull/42012 , and more
[Slack thread](https://vercel.slack.com/archives/C04DUD7EB1B/p1692183798097169 )
Co-authored-by: Steven <229881+styfle@users.noreply.github.com>
2023-09-21 15:30:37 +00:00
vercel-release-bot
e9148eda2a
v13.5.3-canary.0
2023-09-21 09:07:13 +00:00
vercel-release-bot
aea80aa53f
v13.5.2
2023-09-20 16:19:18 +00:00
vercel-release-bot
0afffdd024
v13.5.2-canary.2
2023-09-20 15:29:17 +00:00
vercel-release-bot
72434c2737
v13.5.2-canary.1
2023-09-20 12:53:30 +00:00
vercel-release-bot
ac1c062f4f
v13.5.2-canary.0
2023-09-20 10:49:22 +00:00
Jake Boone
3cd4b975c3
create-next-app templates: Change bun run dev commands to bun dev (#55603 )
...
[As of Bun v1.0.0](https://bun.sh/blog/bun-v1.0#changelog-since-v0-8 ), `bun dev` runs the "dev" script from package.json. Therefore, as with Yarn and pnpm, the "run" command is not necessary.
This PR changes the `create-next-app` README templates to show `bun dev` instead of `bun run dev`.
2023-09-19 19:04:33 +00:00
vercel-release-bot
0c1c7f847e
v13.5.1
2023-09-19 17:20:54 +00:00
vercel-release-bot
974428583e
v13.5.1-canary.1
2023-09-19 16:31:03 +00:00
vercel-release-bot
c652dc8811
v13.5.1-canary.0
2023-09-19 16:10:26 +00:00
vercel-release-bot
ffafad2c35
v13.5.0
2023-09-19 15:36:42 +00:00
vercel-release-bot
4a589ed83d
v13.4.20-canary.41
2023-09-19 13:56:12 +00:00
vercel-release-bot
d01ab6165e
v13.4.20-canary.40
2023-09-18 23:29:58 +00:00
vercel-release-bot
41c89f0cd8
v13.4.20-canary.39
2023-09-18 20:12:27 +00:00
vercel-release-bot
4f98dc6f26
v13.4.20-canary.38
2023-09-18 19:09:41 +00:00
YOSHIKI
7db5c64e94
docs: add bun run dev command to template readme for create-next-app ( #55504 )
...
## For Contributors
### Improving Documentation
- [x] Run `pnpm prettier-fix` to fix formatting issues before opening the PR.
- [x] Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide
### What?
add bun run dev command to template readme for create-next-app
2023-09-18 18:18:58 +00:00
vercel-release-bot
36e12a7415
v13.4.20-canary.37
2023-09-18 14:05:39 +00:00
vercel-release-bot
b2facf5811
v13.4.20-canary.36
2023-09-18 12:03:44 +00:00
vercel-release-bot
096d910423
v13.4.20-canary.35
2023-09-18 09:27:39 +00:00
vercel-release-bot
8fd2ad27b9
v13.4.20-canary.34
2023-09-18 06:25:35 +00:00
vercel-release-bot
981e8fa945
v13.4.20-canary.33
2023-09-16 10:38:10 +00:00
vercel-release-bot
e262627bd9
v13.4.20-canary.32
2023-09-15 19:55:16 +00:00
vercel-release-bot
15292da332
v13.4.20-canary.31
2023-09-15 06:05:22 +00:00
vercel-release-bot
18d703e0b7
v13.4.20-canary.30
2023-09-14 21:50:52 +00:00
vercel-release-bot
be38d02349
v13.4.20-canary.29
2023-09-14 20:56:41 +00:00
vercel-release-bot
800fdc11ae
v13.4.20-canary.28
2023-09-13 22:47:32 +00:00
vercel-release-bot
32e066ff6c
v13.4.20-canary.27
2023-09-13 17:38:35 +00:00
vercel-release-bot
366885f387
v13.4.20-canary.26
2023-09-12 13:20:27 +00:00
vercel-release-bot
8e1626851e
v13.4.20-canary.25
2023-09-12 10:34:24 +00:00
vercel-release-bot
476fe4a1f6
v13.4.20-canary.24
2023-09-11 20:24:23 +00:00
vercel-release-bot
c6ce87f021
v13.4.20-canary.23
2023-09-08 21:41:11 +00:00
vercel-release-bot
d61c6ba4aa
v13.4.20-canary.22
2023-09-08 21:10:48 +00:00
vercel-release-bot
904d8eed39
v13.4.20-canary.21
2023-09-07 23:18:04 +00:00
vercel-release-bot
3062462156
v13.4.20-canary.20
2023-09-07 16:06:41 +00:00
vercel-release-bot
9bb9f07e82
v13.4.20-canary.19
2023-09-07 06:36:23 +00:00
vercel-release-bot
cdfb9de498
v13.4.20-canary.18
2023-09-05 22:49:40 +00:00
vercel-release-bot
1b844600ce
v13.4.20-canary.17
2023-09-05 18:20:51 +00:00
vercel-release-bot
7a1924ed6d
v13.4.20-canary.16
2023-09-04 11:58:51 +00:00
vercel-release-bot
d172e7b72c
v13.4.20-canary.15
2023-08-31 22:23:23 +00:00
vercel-release-bot
e1cc97f3e4
v13.4.20-canary.14
2023-08-31 17:24:11 +00:00
vercel-release-bot
fe191f8e54
v13.4.20-canary.13
2023-08-31 01:53:14 +00:00
vercel-release-bot
928c4c097c
v13.4.20-canary.12
2023-08-29 10:42:17 +00:00
vercel-release-bot
5b62f15586
v13.4.20-canary.11
2023-08-28 14:27:50 +00:00
vercel-release-bot
1491d4c2ed
v13.4.20-canary.10
2023-08-28 13:30:48 +00:00
vercel-release-bot
529a1be6c1
v13.4.20-canary.9
2023-08-25 21:26:50 +00:00
vercel-release-bot
dbfcfd75b7
v13.4.20-canary.8
2023-08-25 14:28:07 +00:00
vercel-release-bot
d8b1ad41a7
v13.4.20-canary.7
2023-08-25 13:43:11 +00:00
vercel-release-bot
96f571218b
v13.4.20-canary.6
2023-08-24 22:34:30 +00:00
vercel-release-bot
9bcd570bc1
v13.4.20-canary.5
2023-08-24 16:38:19 +00:00
vercel-release-bot
80e6f07f01
v13.4.20-canary.4
2023-08-23 23:32:02 +00:00
vercel-release-bot
93e4e6d438
v13.4.20-canary.3
2023-08-23 13:13:36 +00:00
vercel-release-bot
8bbf674a4d
v13.4.20-canary.2
2023-08-22 12:43:03 +00:00
Steven
f6d2aa09de
fix: minimum node version 16.14.0 ( #54331 )
...
- Fixes https://github.com/vercel/next.js/issues/54269
- Related to https://github.com/vercel/next.js/pull/54285
2023-08-22 08:58:53 +00:00
vercel-release-bot
1a56fb9483
v13.4.20-canary.1
2023-08-21 22:41:53 +00:00
vercel-release-bot
f1c286fff2
v13.4.20-canary.0
2023-08-20 12:56:16 +00:00
vercel-release-bot
d96e0258de
v13.4.19
2023-08-19 00:23:31 +00:00
vercel-release-bot
1cf4aa6e51
v13.4.19-canary.0
2023-08-18 23:39:41 +00:00
vercel-release-bot
87b66f64e5
v13.4.18
2023-08-18 00:16:08 +00:00
vercel-release-bot
89ed4dd105
v13.4.18-canary.0
2023-08-17 22:11:33 +00:00
vercel-release-bot
236075362a
v13.4.17
2023-08-17 09:32:20 +00:00
vercel-release-bot
645ba004d6
v13.4.17-canary.2
2023-08-17 08:55:11 +00:00
vercel-release-bot
fc3bf373c5
v13.4.17-canary.1
2023-08-17 07:33:02 +00:00
vercel-release-bot
93259caac4
v13.4.17-canary.0
2023-08-16 21:11:24 +00:00
stefanprobst
42227559c6
fix: don't add forceConsistentCasingInFileNames to tsconfig when ts version >= 5.0 ( #51564 )
...
Currently, Next.js enforces that `forceConsistentCasingInFileNames: true` is added to a user's `tsconfig.json`.
This PR removes that behavior for CNA templates, and when the typescript version is >= 5.0.0, because since ts 5.0 `forceConsistentCasingInFileNames` is `true` by default. See https://devblogs.microsoft.com/typescript/announcing-typescript-5-0/
related: https://github.com/vercel/next.js/issues/45617
2023-08-15 19:12:40 +00:00
vercel-release-bot
2fac86480c
v13.4.16
2023-08-15 01:03:24 +00:00
vercel-release-bot
33d9bf2a8f
v13.4.16-canary.1
2023-08-15 00:42:45 +00:00
vercel-release-bot
4d0aaafdef
v13.4.16-canary.0
2023-08-14 22:26:27 +00:00
vercel-release-bot
6306ec1c1d
v13.4.15
2023-08-14 16:40:09 +00:00
vercel-release-bot
242cdca8e0
v13.4.15-canary.0
2023-08-14 16:01:53 +00:00
vercel-release-bot
4ee4458d46
v13.4.14
2023-08-14 10:46:46 +00:00
vercel-release-bot
e53f3af934
v13.4.14-canary.5
2023-08-14 07:58:37 +00:00
vercel-release-bot
df6ec96ab2
v13.4.14-canary.4
2023-08-14 04:47:55 +00:00
vercel-release-bot
261db496f7
v13.4.14-canary.3
2023-08-12 21:41:13 +00:00
