mirror of https://github.com/vercel/next.js.git synced 2026-09-20 02:25:18 +08:00

Files

T

History

Ben Gubler 41e39426eb Remove automatic linting from build (#83136 )

### What?
This PR removes the automatic ESLint linting that previously ran during `next build`. The documentation has been updated to reflect this change.

### Why?
As part of Next.js 16, we're removing the automatic build-time linting that was previously included in the build process. This gives developers more control over when linting runs by explicitly invoking their linter via npm scripts.

### How?
- Updated documentation to clarify that automatic build-time linting has been removed in Next.js 16
- Removed the `runLint` parameter and related linting code from the build process
- Removed the `verifyAndLint.ts` file which is no longer needed
- Simplified type checking code by removing lint-related functionality
- Removed ESLint telemetry during builds

2025-10-08 16:35:07 -07:00

public

…

src

…

.gitignore

examples: update gitignore files for parity for yarn recommendations (#71956 )

2024-12-17 01:24:53 +00:00

package.json

Remove automatic linting from build (#83136 )

2025-10-08 16:35:07 -07:00

README.md

examples: fix readmes (#78483 )

2025-04-23 20:48:58 -05:00

tsconfig.json

Use the automatic runtime for type checking (#83159 )

2025-09-02 12:35:42 +02:00

README.md

Zustand example

This example shows how to integrate Zustand in Next.js.

This is an example on how you can use Zustand with Next.js.

All Client Components have access to the Zustand store using useStore() returned store.ts file.

Deploy your own

How to use

Execute create-next-app with npm, Yarn, or pnpm to bootstrap the example:

npx create-next-app --example with-zustand with-zustand-app

yarn create next-app --example with-zustand with-zustand-app

pnpm create next-app --example with-zustand with-zustand-app

Deploy it to the cloud with Vercel (Documentation).