chore(deps): update devdependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@anolilab/eslint-config (source)	^5.0.8 -> ^5.0.10
@anolilab/semantic-release-preset (source)	^3.1.0 -> ^3.1.1
@axe-core/react	^4.7.2 -> ^4.7.3
@next/eslint-plugin-next	^13.4.5 -> ^13.4.6
@prisma/client (source)	4.15.0 -> 4.16.0
@types/node (source)	18.16.17 -> 18.16.18
@types/react (source)	^18.2.11 -> ^18.2.13
@types/react-dom (source)	^18.2.4 -> ^18.2.6
@vitejs/plugin-react (source)	^4.0.0 -> ^4.0.1
@vitest/coverage-v8 (source)	^0.32.0 -> ^0.32.2
eslint (source)	^8.42.0 -> ^8.43.0
eslint-plugin-jsonc (source)	^2.8.0 -> ^2.9.0
next (source)	^13.4.5 -> ^13.4.6
prisma (source)	4.15.0 -> 4.16.0
swagger-ui-dist	^4.19.0 -> ^4.19.1
swagger-ui-react	^4.19.0 -> ^4.19.1
webpack	^5.86.0 -> ^5.87.0

---

Release Notes

anolilab/javascript-style-guide (@​anolilab/eslint-config)

v5.0.10

Compare Source

Bug Fixes

• added missing n in vitest.cofig.* (16fe216)

v5.0.9

Compare Source

Dependencies

• @​anolilab/semantic-release-preset: upgraded to 3.1.1

anolilab/javascript-style-guide (@​anolilab/semantic-release-preset)

v3.1.1

Compare Source

Dependencies

• @​anolilab/package-json-utils: upgraded to 1.3.0

dequelabs/axe-core-npm

v4.7.3

Compare Source

Bug Fixes

• webdriverjs: skip unloaded iframes (#​743) (9cb50eb)

vercel/next.js

v13.4.6

Compare Source

Core Changes

• Fix windows metadata slashes: #​51088
• Do not merge chunkGroups' CSS files: #​51103
• Add unique search query for RSC requests to be cacable on CDN: #​50970
• add turbopack integration tests to CI: #​50904
• Add option for debugging CPU usage: #​51174
• Prefer module fields for RSC server layer: #​51179
• Update next/head warning to link to the correct docs page: #​51013
• Revert "Do not merge chunkGroups' CSS files": #​51193
• fix: helpful error when output: export and next export -o: #​51191
• Strip _rsc query for navigation between app and page: #​51195
• Fix standalone not found: #​51172
• fix(cli): add all available options to cli commands, format them consistently: #​48708
• update storybook example (copy from vercel/vercel): #​50865
• chore: remove useless duplicate code: #​50705
• fix: app router hash scrolling should respect scroll-padding: #​51268
• Fix build error about trace file and edge route: #​50808
• chore(router): fix typo in comment: #​50581
• Add mikroORM to external package list: #​50487
• [docs] Clarify that merely changing extension does not load .md f…: #​49785
• Correct build workers perf issue: #​51271
• Remove edge functions tracking in dev server: #​51122
• app router: fix double fetch on prefetch={false}: #​51292
• Invalidate client cache when cookies have changed in Server Actions: #​51290
• feat(turbopack): enable sassOptions: #​51259
• Route Module Cleanup: #​50936
• Validate i18n locale domain: #​50220
• chore: add dark mode for dev overlay: #​48601
• chore: update next/font/google font list: #​49969
• fix: Incorrect build size outputs for app dir: #​50768
• Simplify server CSS handling: #​51018
• Allow configuring analyzerMode in bundle-analyzer: #​47468
• Revert "Prefer module fields for RSC server layer": #​51316
• Fix Server Actions compiler: #​51318
• Revert "Route Module Cleanup": #​51322
• test(next-dev): hard fail if next-dev runs with turbopack intenral flag: #​51308
• Revert "test(next-dev): hard fail if next-dev runs with turbopack intenral flag": #​51327
• Update Next.js code owners: #​51319
• Fix CSS deploy id case: #​51325
• Update turbopack: #​51336
• Fix shared layer bundling in Edge Runtime: #​51348

Documentation Changes

• Update 01-images.mdx: #​51133
• Update next-image-unconfigured-host.md with correct Remote Patterns Documentation link to new docs: #​49750
• Fixes the link from components/fonts to api/fonts: #​51169
• Docs: Fix useSearchParams link: #​51151
• docs: Improve Actions docs.: #​51145
• docs: clarify usePathname usage as client hook.: #​51146
• Fix a typo: #​51176
• docs: fix prettier error: #​51182
• Update static assets page to filter out information: #​51180
• Makes codeblock language and filename extensions consistent: #​51056
• Fix a mistake URL in "docs/generate-metadata.mdx/metadataBase": #​51199
• Add separate lines to eslint prompt in 02-eslint.mdx: #​51143
• [Docs][CSS-in-JS]: Update Vanilla Extract link: #​51192
• Fix typo on strategy: #​51189
• app-icons: correct valid route segments for icon/favicon/apple-icon : #​51188
• docs: fix typos: #​51185
• Adds Note to Good to know consistency: #​51080
• docs: fix prettier lint: #​51222
• [docs] Add missing Edge Runtime APIs: #​51224
• docs: Add Tolgee to internationalization section: #​49754
• Clarify the limitations of NEXT_PUBLIC_: #​49105
• Update 02-fonts.mdx: #​51249
• Fix middleware documentation: #​48876
• docs: fixed a typo in parallel routes: #​51267
• Update module-path-aliases.md: #​43592
• CSS concatenation order matches the import order: #​39889
• Fix broken link: #​51281
• Fix broken links: #​51285
• Update images.mdx: #​51275
• Docs: Remove extra word in 03-scripts.mdx: #​51304
• Update example of Server Actions HoC: #​51299
• Adds env suggestions: #​51312
• docs: fix the url of router event: #​51339

Example Changes

• Fix with typescript stripe example fixes #​50541: #​50574
• fix: cypress component testing - fixes #​50283: #​50303
• fix deprecated configureStore in with-redux-saga example: #​50342
• Show how to utilize the provided .env file in the docker-compose file: #​50712
• update(examples): Update with-sentry example: #​47855
• Update Player.tsx to improve code readability and styling.: #​50275
• Update Docker examples to use Compose v2 command: #​51134
• with-facebook-pixel: new implementation with app folder: #​49880
• change strapi example to latest one - fixes #​51332: #​51334
• Auth0 V2 migration update: #​45302
• examples: migrate with-elasticsearch to TypeScript: #​44842

Misc Changes

• Fix getting last stable release stats: #​51106
• ci(workflow): consolidate bytesize upload workflow: #​51110
• ci(workflow): enable test trace upload: #​51107
• Increase remote cache timeout for swc builds: #​51270
• Update flakey rsc streaming test: #​51274
• fix trigger release step
• Update flakey build output test: #​51307
• Skip cargo bench job on release: #​51311
• Ensure swc is copied for release stats: #​51315
• Update flakey deploy tests: #​51314
• Update e2e deploy tests to continue: #​51321

Credits

Huge thanks to @​ijjk, @​huozhi, @​kwonoj, @​shuding, @​shozibabbas, @​omarhoumz, @​jamespearson, @​tristndev, @​sokra, @​leerob, @​AldeonMoriak, @​delbaoliveira, @​manovotny, @​styfle, @​mirismaili, @​tyler-lutz, @​SuttonJack, @​jeremydouglas, @​MaxLeiter, @​Kikobeats, @​JanCizmar, @​mltsy, @​WilderDev, @​Guilleo03, @​Willem-Jaap, @​escwxyz, @​wiredacorn, @​Ethan-Arrowood, @​BaffinLee, @​ztanner, @​greatSumini, @​ciruz, @​kijikunnn, @​DustinsCode, @​riqwan, @​joostdecock, @​nikolovlazar, @​Bowens20832, @​JohnAlbin, @​timneutkens, @​feedthejim, @​wyattjoh, @​gidgudgod, @​maxproske, @​dunklesToast, @​yyuemii, @​mPaella, @​mknichel, @​niko20, @​jyunhanlin, @​mkcy3, and @​valentinpolitov for helping!

prisma/prisma

v4.16.0

Compare Source

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

Highlights

This release promotes the following Preview features to General Availability:

• Prisma Client extensions
• Ordering by nulls first and last
• Count by filtered relation

Prisma Client extensions are Generally Available

Today, we’re very excited to announce that Prisma Client extensions are Generally Available and production-ready! This means you can use the feature without the clientExtensions Preview feature flag.🚀

Prisma Client extensions are a powerful new feature for adding functionality on top of your Prisma Client in a type-safe manner. With this feature, you can create simple, but flexible solutions.

Prisma Client extensions have 4 different types of components that can be included in an extension:

• Result extensions components: add custom fields and methods to query result objects, for example, virtual/computed fields.
• Model extensions components: enable you to add new methods to your models alongside existing model methods such as findMany.
• Query extensions components: let you hook into the lifecycle of a query and perform side effects, modify query arguments, or modify the results in a type-safe way. These are an alternative to middleware that provide complete type safety and can be applied in an ad-hoc manner to different extensions.
• Client extensions components: allow you to add new top-level methods to Prisma Client. You can use this to extend Prisma Client with functionality that isn’t tied to specific models.

const prisma = new PrismaClient().$extends({
  name: "extension-name",
  result: { /* ... */ },
  model: { /* ... */ },
  query: { /* ... */ },
  client: { /* ... */ },
});

You can also create and publish extensions for others to use. Learn more about how to share extensions in our documentation.

More features and changes made to Client Extensions

We also made the following improvements to Prisma Client extensions in preparation for General Availability:

• Added a top-level $allOperations method for query component that captures all model operations as well as top-level raw queries. Refer to our documentation for more information.

  const prisma = new PrismaClient().$extends({
    query: {
      $allOperations({ args, query, operation, model }) {
        /* your extension's logic here */
      }
    }
  })

• Prisma.validator can now also be used for extended types:

  const prisma = new PrismaClient().$extends({/* ... */})
  const data = Prisma.validator(prisma, 'user', 'findFirst', 'select')({
    id: true,
  })

• query callbacks for $queryRaw and $executeRaw will always receive Sql instance as args. This instance can be used to compose a new query using Prisma.sql:

  const prisma = new PrismaClient().$extends({
    query: {
      $queryRaw({ args, query }) {
        return query(Prisma.sql`START TRANSACTION; ${args}; COMMIT;`)
      }
    }
  })

• $on cannot be called after extending Prisma Client. Therefore, if you want to use event handlers together with extensions, we recommend using the $on method before $extends.

  const prisma = new PrismaClient()
    .$on(/* ... */)
    .$extends({/* ... */})

• We updated the import path for utilities used for authoring extension to @prisma/client/extension rather than @prisma/client

  + import { Prisma } from "@​prisma/client/extension"
  - import { Prisma } from "@​prisma/client"

Deprecating Middleware

We also took this opportunity to deprecate Prisma Client’s middleware. We recommend using to using Prisma Client query extension components which can be used to achieve the same functionality and with better type safety.

🚧 Middleware will still be available in Prisma Client’s API. However, we recommend using Prisma Client extensions over middleware.

Ordering by nulls first and last is now Generally Available

Starting with this release, we’re excited to announce that orderByNulls is now Generally Available! This means you can use the feature without the orderByNulls Preview feature flag.🌟

We introduced this feature in 4.1.0 to enable you to sort records with null fields to either appear at the beginning or end of the result.

The following example query sorts posts by updatedAt, with records having a null value at the end of the list:

await prisma.post.findMany({
  orderBy: {
    updatedAt: { sort: 'asc', nulls: 'last' },
  },
})

To learn more about this feature, refer to our documentation.

We’re excited to see what you will build! Feel free to share with us what you build on Twitter, Slack, or Discord.

Count by filtered relation is now Generally Available

This release moves the filteredRelationCount Preview feature to General Availability! This means you can use the feature without the filteredRelationCount Preview feature flag.

We first introduced this feature in 4.3.0 to add the ability to count by filtered relations.

The following query, for example, counts all posts with the title “Hello!”:

await prisma.user.findMany({
  select: {
    _count: {
      select: {
        posts: { where: { title: 'Hello!' } },
      },
    },
  },
})

To learn more about this feature, refer to our documentation.

Introspection warnings for expression indexes

In the last two releases, 4.13.0 and 4.14.0, we added 9 introspection warnings. These warnings surface features in use in your database that cannot currently be represented in the Prisma schema.

In this release, we’re adding one more introspection warning to the list: expression indexes.

On database introspection, the Prisma CLI will surface the feature with a warning, and a comment in your Prisma schema for sections for each feature in use. The warnings will also contain instructions for workarounds on how to use the feature.

Fixes and improvements

Prisma Client

• Attach comments to enum values
• Extend Prisma Client
• Triple-slash Comments should attach to Composite Types
• Nested disconnect fails on MongoDB with extendedWhereUnique
• [ClientExtensions, TypeScript] Fields of custom type aren't available when using the ClientExtensions preview-feature, unless select'd explicitly.
• Extensions incorrect typings generated (casing)
• Misleading error message of prisma generate when running it directly after installing prisma
• Prisma.validator: with clientExtensions enabled, Typescript can no longer compute types
• enum docstrings do not make it to the prisma client
• VScode behavior is very slow while using clientExtensions
• Client extensions in interactive transactions are bound to the base client
• $runCommandRaw is not passing the expected data to middleware or client extension
• PCE: Improve runtime types in raw query extensions
• Sequential transactions run out of order when using client extensions and middleware
• Client Extension: Make .prismaVersion.client available on "@​prisma/client/scripts/default-index"
• Cannot create record with Prisma.DbNull when clientExtensions enabled
• Extended client raw queries fail when using the Prisma.sql helper
• jsonProtocol: array shortcut is missing for distinct field
• Prisma Client Extension: support Prisma.validator
• Prisma Client: make clientExtensions GA
• PCE: Query extensions of $queryRawUnsafe also triggers $allModels.$allOperations
• PCE: $on applied to an extended client is also bound to the parent client
• Type "never" returned from nested properties when using "select" after enabling data proxy + accelerate
• $queryRaw* is broken in interactive transactions together with clientExtensions in 4.16.0-dev.17
• Deploying to an offline environment fails because it tries to download a Prisma engine checksum file
• jsonProtocol: Wrong error message shown for validation error for checked/unchecked types
• Bug: FindXOrThrow don't get batched on the engine

Prisma Migrate

• Allow skipping sha checksum
• Documentation not available in DMMF for MongoDB types
• prisma db pull gets rid of @default(uuid()) on re-introspection

Language tools (e.g. VS Code)

• Go to Definition does not work when target model contains a field with a type name that starts with the same name

Prisma Studio

• Error: spawn xdg-open ENOENT on prisma studio

📺 Join us for another "What's new in Prisma" live stream

Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" live stream.

The stream takes place on YouTube on Thursday, June 22 at 5 pm Berlin | 8 am San Francisco.

vitejs/vite-plugin-react

v4.0.1

Compare Source

• Support Vitest deps.experimentalOptimizer
• Support using components inside web workers (#​181)

vitest-dev/vitest

v0.32.2

Compare Source

   🐞 Bug Fixes

• browser: Don't fail on importing diff-sequences  -  by @​sheremet-va (00b0e)

    View changes on GitHub

v0.32.1

Compare Source

   🚀 Features

• Export registerConsoleShortcuts from vitest/node  -  by @​deot in https://github.com/vitest-dev/vitest/issues/3563 (bc49b)
• expect: Support expect.unreachable  -  by @​fenghan34 and @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3556 (8e385)
• runner: describe/test name support anonymous function  -  by @​btea in https://github.com/vitest-dev/vitest/issues/3562 (3d436)

   🐞 Bug Fixes

• Avoid call stack recursion with large error (fix: #​3060)  -  by @​nathanmmiller and @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3078 and https://github.com/vitest-dev/vitest/issues/3060 (02196)
• Automatically remove define related configuration  -  by @​btea in https://github.com/vitest-dev/vitest/issues/3552 (368b8)
• Import performance from perf_hooks  -  by @​Max10240 and wangbaolong.wbl in https://github.com/vitest-dev/vitest/issues/3578 and https://github.com/vitest-dev/vitest/issues/3579 (24ec8)
• Revert concordance diff, use jest's diff output  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3582 (9c7ea)
• Typo in config suggestion  -  by @​Krisell in https://github.com/vitest-dev/vitest/issues/3583 (68985)
• browser:
  • Change optimized deps to use vitest  -  by @​userquin in https://github.com/vitest-dev/vitest/issues/3580 (b4ac8)
  • Access vi_inject only if it was injected  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3587 (d9e14)
• mocker:
  • Respect namespace import when hoisting vi.mock  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3547 (158c4)
• ui:
  • Navigate to dashboard when re-running tests from coverage page  -  by @​userquin in https://github.com/vitest-dev/vitest/issues/3529 (bc283)
• vite-node:
  • Correctly resolve virtual modules  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3544 (0cbb0)
  • Fix errors caused by commonjs export circular references  -  by @​rxliuli in https://github.com/vitest-dev/vitest/issues/3570 (b097c)

    View changes on GitHub

eslint/eslint

v8.43.0

Compare Source

Features

• 14581ff feat: directive prologue detection and autofix condition in quotes (#​17284) (Francesco Trotta)
• e50fac3 feat: add declaration loc to message in block-scoped-var (#​17252) (Milos Djermanovic)
• 1b7faf0 feat: add skipJSXText option to no-irregular-whitespace rule (#​17182) (Azat S)

Bug Fixes

• 5338b56 fix: normalize cwd passed to ESLint/FlatESLint constructor (#​17277) (Milos Djermanovic)
• 54383e6 fix: Remove no-extra-parens autofix for potential directives (#​17022) (Francesco Trotta)

Documentation

• 8b855ea docs: resubmit pr17061 doc changes (#​17292) (唯然)
• 372722e docs: resubmit pr17012 doc changes (#​17293) (唯然)
• 67e7af3 docs: resubmit custom-rules doc changes (#​17294) (唯然)
• 9e3d77c docs: Resubmit Fix formatting in Custom Rules docs (#​17281) (Milos Djermanovic)
• 503647a docs: Resubmit markVariableAsUsed docs (#​17280) (Nicholas C. Zakas)
• e0cf0d8 docs: Custom rule & plugin tutorial (#​17024) (Ben Perlmutter)
• 8e51ea9 docs: resubmit no-new rule documentation (#​17264) (Nitin Kumar)
• 1b217f8 docs: resubmit Custom Processors documentation (#​17265) (Nitin Kumar)
• 428fc76 docs: resubmit Create Plugins documentation (#​17268) (Nitin Kumar)
• bdca88c docs: resubmit Configuration Files documentation (#​17267) (Nitin Kumar)
• f5c01f2 docs: resubmit Manage Issues documentation (#​17266) (Nitin Kumar)
• b199295 docs: Resubmit custom rules update docs (#​17273) (Ben Perlmutter)
• 0e9980c docs: add new omitLastInOneLineClassBody option to the semi rule (#​17263) (Nitin Kumar)
• cb2560f docs: Resubmit getScope/getDeclaredVariables docs (#​17262) (Nicholas C. Zakas)
• 85d2b30 docs: explain how to include predefined globals (#​17261) (Marcus Wyatt)
• de4d3c1 docs: update flat config default ignore patterns (#​17258) (Milos Djermanovic)
• 3912f3a docs: Improve ignores documentation (#​17239) (Francesco Trotta)
• 35e11d3 docs: fix typos and missing info (#​17257) (Ed Lucas)
• 0bc257c docs: Clarify no-div-regex rule docs (#​17051) (#​17255) (Francesco Trotta)
• 788d836 docs: add references to MIT License (#​17248) (Milos Djermanovic)
• 58aab6b docs: Update README (GitHub Actions Bot)
• 3ef5814 docs: Revert all changes after the license change (#​17227) (Milos Djermanovic)
• 03fc4aa docs: Update README (GitHub Actions Bot)

Chores

• 78350f6 chore: upgrade @​eslint/js@​8.43.0 (#​17295) (Milos Djermanovic)
• 62bf759 chore: package.json update for @​eslint/js release (ESLint Jenkins)
• e0a2448 chore: docs package.license ISC => MIT (#​17254) (唯然)
• 6a0196c chore: use eslint-plugin-eslint-plugin flat configs (#​17204) (Milos Djermanovic)

ota-meshi/eslint-plugin-jsonc

v2.9.0

Compare Source

Minor Changes

• #​243 48d3669 Thanks @​ota-meshi! - feat: add new allowLineSeparatedGroups option to the jsonc/sort-keys rule

swagger-api/swagger-ui

v4.19.1: Swagger UI v4.19.1 Released!

Compare Source

Bug Fixes

• export standalone preset from the npm package (#​8906) (cdd0bdd), closes #​8163
• request-body: fix immutable prop types validation (#​8307) (07a08cd)

webpack/webpack

v5.87.0

Compare Source

New Features

• Implement fetchPriority feature as parser option and magic comment by @​alexander-akait in https://github.com/webpack/webpack/pull/17249
• [CSS] - Introduce 'css/auto' as a css module type by @​ahabhgk in https://github.com/webpack/webpack/pull/16577
• [CSS] - Style-specific fields now automatically resolve in package.json by @​burhanuday in [https://github.com/feat: resolve style fields in package json webpack/webpack#17346](https://togithub

---

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
visulima-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 20, 2023 5:44pm

[github-actions]

Size changes

📦 Next.js Bundle Analysis for nextra_example

This analysis was generated by the Next.js Bundle Analysis action. 🤖

⚠️ Global Bundle Size Increased

Page	Size (compressed)
global	206.83 KB (🟡 +1 B)

Details

The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!

Twenty-six Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page	Size (compressed)	First Load	% of Budget (350 KB)
/404	4.86 KB	211.69 KB	60.48% (+/- <0.01%)
/500	4.85 KB	211.68 KB	60.48% (+/- <0.01%)
/docs/advanced/markdown-import.en-US	9.83 KB	216.66 KB	61.90% (+/- <0.01%)
/docs/advanced/react-native.en-US	6.75 KB	213.58 KB	61.02% (+/- <0.01%)
/docs/advanced/react-native.ru	7.31 KB	214.14 KB	61.18% (+/- <0.01%)
/docs/advanced/scrollbar-x.en-US	5.83 KB	212.66 KB	60.76% (+/- <0.01%)
/docs/getting-started.en-US	12.39 KB	219.22 KB	62.64% (+/- <0.01%)
/docs/getting-started.es-ES	12.02 KB	218.85 KB	62.53% (+/- <0.01%)
/docs/getting-started.ru	12.71 KB	219.54 KB	62.73% (+/- <0.01%)
/docs/options.en-US	6.66 KB	213.49 KB	61.00% (+/- <0.01%)
/docs/options.es-ES	6.81 KB	213.64 KB	61.04% (+/- <0.01%)
/docs/options.ru	7.42 KB	214.25 KB	61.22% (+/- <0.01%)
/docs/pagination.es-ES	17.43 KB	224.26 KB	64.07% (+/- <0.01%)
/docs/pagination.ru	18.38 KB	225.21 KB	64.35% (+/- <0.01%)
/docs/revalidation.en-US	7.79 KB	214.62 KB	61.32% (+/- <0.01%)
/docs/revalidation.es-ES	7.94 KB	214.77 KB	61.36% (+/- <0.01%)
/docs/revalidation.ru	8.54 KB	215.37 KB	61.53% (+/- <0.01%)
/docs/suspense.en-US	6.33 KB	213.16 KB	60.90% (+/- <0.01%)
/docs/suspense.es-ES	6.39 KB	213.22 KB	60.92% (+/- <0.01%)
/docs/suspense.ru	6.76 KB	213.59 KB	61.03% (+/- <0.01%)
/docs/understanding.en-US	8.92 KB	215.75 KB	61.64% (+/- <0.01%)
/docs/understanding.es-ES	8.92 KB	215.75 KB	61.64% (+/- <0.01%)
/index.en-US	8.7 KB	215.53 KB	61.58% (+/- <0.01%)
/index.es-ES	8.47 KB	215.3 KB	61.52% (+/- <0.01%)
/index.ru	8.89 KB	215.72 KB	61.64% (+/- <0.01%)
/remote/graphql-yoga/[[...slug]]	4.86 KB	211.69 KB	60.48% (+/- <0.01%)

Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.