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
Jiachi Liu
e117c000e4
Redesign nextjs logging ( #54713 )
...
The current logging styles has been existed for a while, this PR gives a fresh impression for the logging output from Next.js.
We want to achieve few new goals that makes the output clean, modernized, sweet 🍫 .
Few goals are addressed with this redesign:
## Refresh Impression & Simplification
The new design of logging is much more information centralized and streamlined.
* Given a `ready` message at the begining when compilers are bootstrapped.
* Only show `compiled` event with green check mark indicating succesful compilation, this will merge the unclear `compiling` event which shows `(client and server)` before, now tell you the route compilation info in one line.
hello world app
### `next dev`
#### After vs Before
<img src="https://github.com/vercel/next.js/assets/4800338/9649b340-8241-4756-a2b3-a989f0b74003 " height="120">
<img src="https://github.com/vercel/next.js/assets/4800338/ee181263-3dd4-40d0-9ffc-819a56b45900 " height="120">
### `next build`
#### After vs Before
<img src="https://github.com/vercel/next.js/assets/4800338/5db9829a-9ffc-49f0-b030-93ee92f5c248 " width="360">
<img src="https://github.com/vercel/next.js/assets/4800338/b9527b83-27c8-4426-9c0d-c0d4072b7d58 " width="360">
### error status
#### After vs Before
<img src="https://github.com/vercel/next.js/assets/4800338/00455226-ace7-468b-8d90-0d36bf038489 " height="120">
<img src="https://github.com/vercel/next.js/assets/4800338/1be8c451-d3f0-465c-9ef7-6b0dde7cff85 " height="120">
## Streamlization
If you have customized envs and experiments Next.js will give the brief in the early summary about your network information, env vars, and enabled experimental features
<img src="https://github.com/vercel/next.js/assets/4800338/ca1a7409-1532-46cb-850f-687e61e587b2 " width="400">
## Polish
### fetching logging structure
#### After vs Before
<img src="https://github.com/vercel/next.js/assets/4800338/97526397-dffe-4736-88ed-e5cbe5e945bd " width="400">
<img src="https://github.com/vercel/next.js/assets/4800338/ab77c907-5ab5-48bb-8347-6146d2e60932 " width="400">
### Dedupe Duplicates
The logging is moved from `@next/env` to `next` itself, `@next/env` will only notify the invoker that the env is reloaded. Then the duplicated logs for the env reloading cases can be avoid.
#### After vs Before
<img src="https://github.com/vercel/next.js/assets/4800338/04799295-e739-4035-87aa-61cec962fc39 " width="400">
<img src="https://github.com/vercel/next.js/assets/4800338/e29020c9-0031-4bf3-a21b-8b64633f43a2 " width="400">
### Different indicators
Use unicode text icons for different situation:
* passed -> check mark
* warning -> warning
* error -> red cross
* loading -> circle
<img src="https://github.com/vercel/next.js/assets/4800338/715c34bd-298f-4990-a5d7-e12e455ead44 " width="400">
Co-authored-by: Tim Neutkens <6324199+timneutkens@users.noreply.github.com>
2023-09-05 11:40:00 +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
Shu Ding
5584e5743a
Merge app renderer process ( #54143 )
...
This PR merges the app renderer worker into the router process. This
improves the memory overhead mostly.
There're future work to do to get rid of the IPC server for router and
app renderer, as they're now merged in one process.
Fixes NEXT-1492
2023-08-22 14:38:42 +02: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
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
vercel-release-bot
9229f74b86
v13.4.14-canary.2
2023-08-11 12:02:35 +00:00
vercel-release-bot
d7405b0c28
v13.4.14-canary.1
2023-08-08 14:11:47 +00:00
vercel-release-bot
5ea372d642
v13.4.14-canary.0
2023-08-07 12:49:08 +00:00
vercel-release-bot
498692b698
v13.4.13
2023-08-07 06:57:47 +00:00
vercel-release-bot
1e02a92a94
v13.4.13-canary.18
2023-08-07 01:06:01 +00:00
vercel-release-bot
bc8deab6ef
v13.4.13-canary.17
2023-08-06 20:38:12 +00:00
vercel-release-bot
f47081f15b
v13.4.13-canary.16
2023-08-05 00:20:47 +00:00
vercel-release-bot
324814f2ae
v13.4.13-canary.15
2023-08-04 19:13:19 +00:00
vercel-release-bot
f04dc5ad51
v13.4.13-canary.14
2023-08-04 09:02:27 +00:00
vercel-release-bot
be457445b8
v13.4.13-canary.13
2023-08-03 15:51:26 +00:00
vercel-release-bot
480e3a3939
v13.4.13-canary.12
2023-08-02 17:19:31 +00:00
vercel-release-bot
b1bf7aeefa
v13.4.13-canary.11
2023-08-02 11:15:46 +00:00
vercel-release-bot
e757cac3f4
v13.4.13-canary.10
2023-08-02 09:49:13 +00:00
vercel-release-bot
3a3030882c
v13.4.13-canary.9
2023-08-01 16:30:58 +00:00
Josh Goldberg ✨
fc52e02787
chore: enable typescript-eslint's recommended and stylistic configs internally ( #52948 )
...
Spinning out from #37151 and my draft PR #52845 , this enables the two
basic recommended rulesets from
[typescript-eslint](https://typescript-eslint.io ) for the Next.js
monorepo source code:
*
[`plugin:@typescript-eslint/recommended`](https://typescript-eslint.io/linting/configs#recommended ):
Our base recommended rules that detect common bugs or _(non-stylistic)_
TypeScript bad practices
*
[`plugin:@typescript-eslint/stylistic`](https://typescript-eslint.io/linting/configs#stylistic ):
Our base starting stylistic recommended for keeping codebases visually
consistent and avoiding out-of-practice visual constructs
The process I used is pretty standard (see
https://github.com/typescript-eslint/typescript-eslint/issues/6760 for
other repos it was done on):
1. Enable those base recommended presets
2. Remove any rule settings that are now redundant
3. Reconfigure any rule whose default settings didn't seem to make sense
for this codebase
4. Add a `// Todo: ...` comment, and under it, add a disable for any
rule that immediately reported a lot of complaints
Note that this only enables the presets internally. It doesn't impact
what end-users of published packages such as Next.js or
`create-next-app` experience. That's a separate task in #52845 .
I also didn't fix any existing warning from the `canary` branch. Would
you like me to do that? My preference would be a separate PR to get it
in more quickly.
Any code changes are commented inline.
---------
Co-authored-by: Steven <steven@ceriously.com>
2023-07-31 16:32:54 -07:00
vercel-release-bot
caf5ee80be
v13.4.13-canary.8
2023-07-31 20:06:20 +00:00
vercel-release-bot
82e3d5126a
v13.4.13-canary.7
2023-07-31 17:31:05 +00:00
vercel-release-bot
e575179b3e
v13.4.13-canary.6
2023-07-28 12:32:12 +00:00
vercel-release-bot
0814c82d0b
v13.4.13-canary.5
2023-07-28 00:50:18 +00:00
vercel-release-bot
127c5bbf80
v13.4.13-canary.4
2023-07-27 00:17:07 +00:00
vercel-release-bot
f389d815fd
v13.4.13-canary.3
2023-07-26 04:13:11 +00:00
vercel-release-bot
f89987f09d
v13.4.13-canary.2
2023-07-25 19:56:56 +00:00
vercel-release-bot
87acd0432a
v13.4.13-canary.1
2023-07-25 14:48:22 +00:00
vercel-release-bot
d680975537
v13.4.13-canary.0
2023-07-24 23:10:37 +00:00
vercel-release-bot
552bca46eb
v13.4.12
2023-07-21 20:30:24 +00:00
vercel-release-bot
576cb6ed4f
v13.4.12-canary.0
2023-07-21 19:40:40 +00:00
vercel-release-bot
04ae5be8d0
v13.4.11
2023-07-21 04:28:14 +00:00
vercel-release-bot
5853258d19
v13.4.11-canary.2
2023-07-21 03:49:07 +00:00
vercel-release-bot
0df8aac935
v13.4.11-canary.1
2023-07-20 22:21:52 +00:00
vercel-release-bot
5bf2bbb378
v13.4.11-canary.0
2023-07-18 17:12:06 +00:00
vercel-release-bot
c2a54aaecb
v13.4.10
2023-07-14 09:14:17 +00:00
vercel-release-bot
62aa2d221c
v13.4.10-canary.8
2023-07-14 01:51:38 +00:00
vercel-release-bot
3cde104d64
v13.4.10-canary.7
2023-07-13 19:40:00 +00:00
vercel-release-bot
c56915842a
v13.4.10-canary.6
2023-07-13 02:16:14 +00:00
vercel-release-bot
22cb1bf027
v13.4.10-canary.5
2023-07-12 16:38:56 +00:00
vercel-release-bot
2441ad4760
v13.4.10-canary.4
2023-07-12 06:45:31 +00:00
vercel-release-bot
63a6cdaf53
v13.4.10-canary.3
2023-07-10 23:02:55 +00:00
vercel-release-bot
4e710645f8
v13.4.10-canary.2
2023-07-10 14:44:00 +00:00
vercel-release-bot
62c2c5abc2
v13.4.10-canary.1
2023-07-10 08:01:26 +00:00
vercel-release-bot
b2c6bc4572
v13.4.10-canary.0
2023-07-07 11:14:32 +00:00
vercel-release-bot
1045644655
v13.4.9
2023-07-06 20:50:37 +00:00
vercel-release-bot
21392cb4e0
v13.4.9-canary.3
2023-07-06 17:07:58 +00:00
vercel-release-bot
0b470753b7
v13.4.9-canary.2
2023-07-05 10:26:56 +00:00
Tobias Koppers
fd508b086c
fix env reloading for turbopack ( #52194 )
...
### What?
fixes WEB-1258
2023-07-04 19:28:34 +00:00
vercel-release-bot
4f75c79938
v13.4.9-canary.1
2023-07-04 08:30:06 +00:00
vercel-release-bot
f60b5621ac
v13.4.9-canary.0
2023-07-04 00:05:08 +00:00
vercel-release-bot
b4a875eb57
v13.4.8
2023-07-03 17:00:28 +00:00
vercel-release-bot
eca315308a
v13.4.8-canary.15
2023-07-03 10:21:27 +00:00
vercel-release-bot
9f6cf08fd4
v13.4.8-canary.14
2023-06-30 22:36:17 +00:00
