vercel-release-bot
6387c9cbcb
v14.0.4-canary.43
2023-12-05 23:22:24 +00:00
vercel-release-bot
2003f5f848
v14.0.4-canary.42
2023-12-05 16:33:54 +00:00
vercel-release-bot
b2084ea0ac
v14.0.4-canary.41
2023-12-05 13:10:07 +00:00
vercel-release-bot
708f85b9df
v14.0.4-canary.40
2023-12-04 22:27:15 +00:00
Jiachi Liu
42b87892e4
Fix non bundler module resolution in ts for third-parties pkg ( #59244 )
2023-12-04 20:40:25 +01:00
vercel-release-bot
445e705028
v14.0.4-canary.39
2023-12-04 11:05:59 +00:00
vercel-release-bot
d9e58034c3
v14.0.4-canary.38
2023-12-04 09:53:49 +00:00
vercel-release-bot
141dbb2663
v14.0.4-canary.37
2023-12-03 15:32:15 +00:00
vercel-release-bot
c530664c13
v14.0.4-canary.36
2023-12-02 23:21:42 +00:00
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
Janicklas Ralph
3ec0551fa7
Add performance.mark for next/third-parties for feature measurement ( #57439 )
...
### What?
Adding a `performance.mark` for next/third-parties for feature measurement
### Why?
We’re working with the Chrome Speed Metrics team to develop an API to better identify specific features used by frameworks and/or CMS platforms. Instead of a entirely new API surface, we've agreed to use `performance.mark` as the signal along with mark_use_counter as a signature.
In the past, we've used HTML attributes for Next which have been helpful, but this will improve the accuracy of our feature detection. In this instance, this will better help us analyze and compare sites that use `@next/third-parties` versus those that don't, and to see if our efforts are actually improving performance.
It's worth noting that this metric will have a public arm, but we're starting to incorporate its usage now to gather early data. performance.mark calls are indeed low-overhead and shouldn't affect loading/rendering performance whatsoever.
2023-11-15 17:48:38 +00:00
