2 min read

Conformance changelog

Find out what's new in each release of Conformance.
Table of Contents

Conformance is available on Enterprise plans

pnpm
yarn
npm

pnpm update --latest --recursive @vercel-private/conformance

Initial release of Conformance.

This minor update introduces new rules to improve Next.js app performance, enhancements to the CLI output, and improvements to our telemetry. While telemetry improvements are not directly user-facing, they enhance our ability to monitor and optimize performance.

The following new rules have been added:

  • NEXTJS_NO_ASYNC_PAGE: Ensures that the exported Next.js page component and its transitive dependencies are not asynchronous, as that blocks the rendering of the page.
  • NEXTJS_NO_ASYNC_LAYOUT: Ensures that the exported Next.js layout component and its transitive dependencies are not asynchronous, as that can block the rendering of the layout and the rest of the page.
  • NEXTJS_USE_NATIVE_FETCH: Requires using native fetch which Next.js polyfills, removing the need for third-party fetch libraries.
  • NEXTJS_USE_NEXT_FONT: Requires using next/font (when possible), which optimizes fonts for improved privacy and performance.
  • NEXTJS_USE_NEXT_IMAGE: Requires that next/image is used for all images for improved performance.
  • NEXTJS_USE_NEXT_SCRIPT: Requires that next/script is used for all scripts for improved performance.

This minor update introduces a new rule, and improvements to both NEXTJS_NO_ASYNC_LAYOUT and NEXTJS_NO_ASYNC_PAGE.

The following new rules have been added:

  • REQUIRE_NODE_VERSION_FILE: Requires that workspaces have a valid Node.js version file (.node-version or .nvmrc) file defined.

This patch updates some Conformance dependencies for performance and security, and improves handling of edge case for both NEXTJS_NO_ASYNC_LAYOUT and NEXTJS_NO_ASYNC_PAGE.

Last updated on February 21, 2024