archive/rsnext
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
rsnext/.eslintignore

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

48 lines
1.5 KiB
Text
Raw Permalink Normal View History

Improve linting rules to catch more errors (#9374) * Update `packages/` * Update examples * Update tests * Update bench * Update top level files * Fix build * trigger
2019-11-11 04:24:53 +01:00
node_modules
**/.next/**
**/_next/**
chore: Add `.vscode` to eslintignore (#48020) ### What? Add `.vscode` to `.eslintignore`. ### Why? We ignore `.vscode` folder in our tests, but Next.js itself creates it so manually running tests locally will causing them to be added. That causes ESLint to fail because it checks JSON files inside `.vscode` folder.
2023-04-07 17:51:26 +02:00
**/.vscode/**
Improve linting rules to catch more errors (#9374) * Update `packages/` * Update examples * Update tests * Update bench * Update top level files * Fix build * trigger
2019-11-11 04:24:53 +01:00
**/dist/**
Adds ESLint with default rule-set (#23702) This PR re-includes ESLint with some notable changes, namely a guided setup similar to how TypeScript is instantiated in a Next.js application. To add ESLint to a project, developers will have to create an `.eslintrc` file in the root of their project or add an empty `eslintConfig` object to their `package.json` file. ```js touch .eslintrc ``` Then running `next build` will show instructions to install the required packages needed: <img width="862" alt="Screen Shot 2021-04-19 at 7 38 27 PM" src="https://user-images.githubusercontent.com/12476932/115316182-dfd51b00-a146-11eb-830c-90bad20ed151.png"> Once installed and `next build` is run again, `.eslintrc` will be automatically configured to include the default config: ```json { "extends": "next" } ``` In addition to this change: - The feature is now under the experimental flag and requires opt-in. After testing and feedback, it will be switched to the top-level namespace and turned on by default. - A new ESLint shareable configuration package is included that can be extended in any application with `{ extends: 'next' }` - This default config extends recommended rule sets from [`eslint-plugin-react`](https://www.npmjs.com/package/eslint-plugin-react), [`eslint-plugin-react-hooks`](https://www.npmjs.com/package/eslint-plugin-react-hooks), and [`eslint-plugin-next`](https://www.npmjs.com/package/@next/eslint-plugin-next) - All rules in [`eslint-plugin-next`](https://www.npmjs.com/package/@next/eslint-plugin-next) have been modified to include actionable links that show more information to help resolve each issue
2021-04-30 13:09:07 +02:00
e2e-tests/**
Add TypeGen to Sanity example (#64198) Adds support for the [newly introduced Sanity TypeGen](https://www.sanity.io/blog/introducing-sanity-typegen)! 🥳
2024-04-12 17:28:35 +02:00
examples/cms-sanity/sanity.types.ts
Adds ESLint with default rule-set (#23702) This PR re-includes ESLint with some notable changes, namely a guided setup similar to how TypeScript is instantiated in a Next.js application. To add ESLint to a project, developers will have to create an `.eslintrc` file in the root of their project or add an empty `eslintConfig` object to their `package.json` file. ```js touch .eslintrc ``` Then running `next build` will show instructions to install the required packages needed: <img width="862" alt="Screen Shot 2021-04-19 at 7 38 27 PM" src="https://user-images.githubusercontent.com/12476932/115316182-dfd51b00-a146-11eb-830c-90bad20ed151.png"> Once installed and `next build` is run again, `.eslintrc` will be automatically configured to include the default config: ```json { "extends": "next" } ``` In addition to this change: - The feature is now under the experimental flag and requires opt-in. After testing and feedback, it will be switched to the top-level namespace and turned on by default. - A new ESLint shareable configuration package is included that can be extended in any application with `{ extends: 'next' }` - This default config extends recommended rule sets from [`eslint-plugin-react`](https://www.npmjs.com/package/eslint-plugin-react), [`eslint-plugin-react-hooks`](https://www.npmjs.com/package/eslint-plugin-react-hooks), and [`eslint-plugin-next`](https://www.npmjs.com/package/@next/eslint-plugin-next) - All rules in [`eslint-plugin-next`](https://www.npmjs.com/package/@next/eslint-plugin-next) have been modified to include actionable links that show more information to help resolve each issue
2021-04-30 13:09:07 +02:00
examples/with-eslint/**
[examples] with-ts-eslint-jest example app (#12025) * set up with-ts-eslint-jest example app * eslint ignore new app bc it has a conflicting eslintrc * make eslint + husky setup manual * clarify app README setup notes * move page tests out of pages/ dir * Simplifying configs * extend "prettier" * format fix * Updated rules * Added husky configs and removed debug option * Removed notes and configuration * Updated pages * Added links to readme * Added example to .prettierignore * Updated snap * Make the lint work Co-authored-by: Luis Alvarez D <luis@vercel.com>
2020-05-25 20:16:06 +02:00
examples/with-typescript-eslint-jest/**
Pre-ncc compiled packages to prevent re-nccing unnecessarily (#11569) * Pre-ncc compiled packages to prevent re-nccing unnecessarily * Add compiled files * Re-run pre-ncc step * Add check to workflow to ensure pre-compiled doesnt need updating * Update check-pre-compiled script * Add handling for lower case license while nccing * bump Co-authored-by: Joe Haddad <joe.haddad@zeit.co>
2020-04-07 15:42:16 +02:00
examples/with-kea/**
[ESLint] Remove error when file patterns are unmatched + ESLint setup changes (#27119) Co-authored-by: Tim Neutkens <tim@timneutkens.nl>
2021-07-16 20:19:08 +02:00
examples/with-custom-babel-config/**
examples/with-flow/**
Use recommended pattern in testing example (#28404) * Use recommended pattern in testing example Since the official linter for testing library, `eslint-plugin-testing-library` recommends using `screen` to write queries, this MR updates the testing library example to follow the pattern recommended by the linter. > DOM Testing Library (and other Testing Library frameworks built on top of it) exports a screen object which has every query (and a debug method). This works better with autocomplete and makes each test a little simpler to write and maintain. > This rule aims to force writing tests using built-in queries directly from screen object rather than destructuring them from render result. Given the screen component does not expose utility methods such as rerender() or the container property, it is correct to use the render returned value in those scenarios. See the `prefer-screen-queries` rules docs for more info: https://github.com/testing-library/eslint-plugin-testing-library/blob/main/docs/rules/prefer-screen-queries.md * Update devDependencies * Install and configure test linting * Use recommended pattern in test * Update test names for consistency * Update docs * Set jest environment in each file * Use root true in `with-jest` eslint config * Ensure nested .eslintrcs are not loaded for repo lint Co-authored-by: jj@jjsweb.site <jj@jjsweb.site>
2021-08-25 19:33:57 +02:00
examples/with-jest/**
[ESLint] Remove error when file patterns are unmatched + ESLint setup changes (#27119) Co-authored-by: Tim Neutkens <tim@timneutkens.nl>
2021-07-16 20:19:08 +02:00
examples/with-mobx-state-tree/**
examples/with-mobx/**
refactor: Latest Tigris sdk and example using decorators (#44256)
2023-01-19 05:44:18 +01:00
examples/with-tigris/db/models/todoItems.ts
Move core files to src folder and move JS files to TypeScript (#44405)
2023-01-03 10:05:50 +01:00
packages/next/src/bundles/webpack/packages/*.runtime.js
packages/next/src/bundles/webpack/packages/lazy-compilation-*.js
packages/next/src/compiled/**/*
Create React Refresh Utils (#12006) * Create React Refresh Utils * Fix Linting * Update Prettier Ignore * fix rules
2020-04-18 19:55:10 +02:00
packages/react-refresh-utils/**/*.js
[Fast Refresh] Redesigned Runtime Error Experience (#12222)
2020-04-30 16:50:25 +02:00
packages/react-dev-overlay/lib/**
Experimental: React Refresh Support (#12008) * Add Fast Refresh Support * Add Basic Acceptance Test * Increase delay * fix version * Ignore test files * Update packages/next/build/webpack/loaders/next-babel-loader.js * Copy tests * Redo test style * drop directory * fix compile * fix remove function * Update helpers
2020-04-19 19:58:31 +02:00
**/__tmp__/**
Move next-codemod to Next.js monorepo (#15536)
2020-08-10 11:14:53 +02:00
.github/actions/next-stats-action/.work
packages/next-codemod/transforms/__testfixtures__/**/*
packages/next-codemod/transforms/__tests__/**/*
packages/next-codemod/**/*.js
packages/next-codemod/**/*.d.ts
Allow pages to be async modules to enable top-level-await (#17590) Co-authored-by: JJ Kasper <jj@jjsweb.site> Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2020-10-14 11:55:42 +02:00
packages/next-env/**/*.d.ts
feat(create-next-app): add `--ts, --typescript` support (#24655) Co-authored-by: Tim Neutkens <timneutkens@me.com>
2021-05-07 10:08:16 +02:00
packages/create-next-app/templates/**
Unignore `test/**/*.test.*` for ESLint (#66415)
2024-06-03 18:15:29 +02:00
test/integration/eslint/**/*.js
test/integration/script-loader/**/*.js
test/development/basic/legacy-decorators/**/*.js
Add decoratorMetadata flag if enabled by tsconfig (#32914) fixes #32913 Adds support for decorator metadata in SWC when enabled through ts/jsconfig. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have helpful link attached, see `contributing.md` ## Feature - [x] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [x] Related issues linked using `fixes #number` - [x] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `yarn lint` Co-authored-by: JJ Kasper <22380829+ijjk@users.noreply.github.com>
2022-02-06 17:48:09 +01:00
test/production/emit-decorator-metadata/**/*.js
Unignore `test/**/*.test.*` for ESLint (#66415)
2024-06-03 18:15:29 +02:00
!test/**/*.test.*
Improve RSC plugin to provide better errors (#42435) This PR improves the RSC plugin for SWC to throw an error when the `"use client"` directive is in the top level, but not before other statements / expressions. For example: Code: ```js import 'react' 'use client' ``` Error: ``` The "use client" directive must be placed before other expressions. Move it to the top of the file to resolve this issue. ,---- 3 | 'use client' : ^^^^^^^^^^^^ `---- ``` ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [x] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm build && pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) Co-authored-by: JJ Kasper <jj@jjsweb.site>
2022-11-24 02:26:38 +01:00
test/e2e/app-dir/rsc-errors/app/swc/use-client/page.js
Adds ESLint with default rule-set (#23702) This PR re-includes ESLint with some notable changes, namely a guided setup similar to how TypeScript is instantiated in a Next.js application. To add ESLint to a project, developers will have to create an `.eslintrc` file in the root of their project or add an empty `eslintConfig` object to their `package.json` file. ```js touch .eslintrc ``` Then running `next build` will show instructions to install the required packages needed: <img width="862" alt="Screen Shot 2021-04-19 at 7 38 27 PM" src="https://user-images.githubusercontent.com/12476932/115316182-dfd51b00-a146-11eb-830c-90bad20ed151.png"> Once installed and `next build` is run again, `.eslintrc` will be automatically configured to include the default config: ```json { "extends": "next" } ``` In addition to this change: - The feature is now under the experimental flag and requires opt-in. After testing and feedback, it will be switched to the top-level namespace and turned on by default. - A new ESLint shareable configuration package is included that can be extended in any application with `{ extends: 'next' }` - This default config extends recommended rule sets from [`eslint-plugin-react`](https://www.npmjs.com/package/eslint-plugin-react), [`eslint-plugin-react-hooks`](https://www.npmjs.com/package/eslint-plugin-react-hooks), and [`eslint-plugin-next`](https://www.npmjs.com/package/@next/eslint-plugin-next) - All rules in [`eslint-plugin-next`](https://www.npmjs.com/package/@next/eslint-plugin-next) have been modified to include actionable links that show more information to help resolve each issue
2021-04-30 13:09:07 +02:00
test-timings.json
Extract next-swc Rust code into its own package (#31635) Co-authored-by: JJ Kasper <jj@jjsweb.site> Co-authored-by: Tim Neutkens <tim@timneutkens.nl> Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2021-11-21 12:59:56 +01:00
packages/next-swc/crates/**
Optimize webpack memory cache garbage collection (#54397) ## What Adds a reworked version of webpack's [built-in memory cache garbage collection plugin](https://github.com/webpack/webpack/blob/853bfda35a0080605c09e1bdeb0103bcb9367a10/lib/cache/MemoryWithGcCachePlugin.js#L15) that is more aggressive in cleaning up unused modules than the default. The default marks 1/5th of the modules as "up for potentially being garbage collected". The new plugin always checks all modules. In my testing this does not cause much overhead compared to the current approach which leverages writing to two separate maps. The change also makes the memory cache eviction more predictable: when an item has not been accessed for 5 compilations it is evicted from the memory cache, it could still be in the disk cache. In order to test this change I had to spin up the benchmarks but these were a bit outdated so I've cleaned up the benchmark applications. --------- Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2023-08-23 15:46:32 +02:00
bench/nested-deps/**
bench/nested-deps-app-router/**
Add bench application with heavy dependencies (#66564) ## What? Work in progress, I'm collecting some dependencies that we keep seeing in traces of slow compilation, makes it easier to optimize these. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2024-06-12 15:05:47 +02:00
bench/heavy-npm-deps/**
Add typedef for next-bundle-analyzer (#35075) * Add typedef for next-bundle-analyzer * Update package.json * update type Co-authored-by: JJ Kasper <jj@jjsweb.site>
2022-05-22 23:32:20 +02:00
packages/next-bundle-analyzer/index.d.ts
examples(with-typescript-graphql): migrate to Yoga v3 and codegen new `preset: client` (#41597) Co-authored-by: Balázs Orbán <info@balazsorban.com>
2022-10-24 21:03:08 +02:00
examples/with-typescript-graphql/lib/gql/
ci: report daily turbo integration test results from this repo (#58965) ### What? A follow up for #58267 and #58394. We no longer need the git branch for history it's stored in datadog now and we also decided that we no longer need slack reporting. Closes PACK-2039 --------- Co-authored-by: Tim Neutkens <tim@timneutkens.nl>
2023-12-04 16:18:42 +01:00
test/development/basic/hmr/components/parse-error.js
docs(turbopack): conslidate existing links (#62034) ### What? This PR improves turbopack documentation, mostly collects existing documents into a single place. Also, adds a support to render mermaid diagram. Closes PACK-2488
2024-02-14 18:12:33 +01:00
packages/next-swc/docs/assets/**/*
Use local AMP validator to reduce test flakiness (#63838) We've seen test flakiness from the upstream AMP resource being unavailable so this pulls that resource to the repo and uses that instead. x-ref: [slack thread](https://vercel.slack.com/archives/C04KC8A53T7/p1711643629072819) Closes NEXT-2961
2024-03-28 21:25:35 +01:00
test/lib/amp-validator-wasm.js
test/production/pages-dir/production/fixture/amp-validator-wasm.js
Improve top level await coverage (#64508) ## What? - Changes webpack output target to `es6` (required for `async function` output) - Adds tests for top level await in server components and client components (App Router) - Converted the async-modules tests to `test/e2e` - Has one skipped test that @gnoff is going to look into. This shouldn't block merging this PR 👍 Adds additional tests for top level `await`. Since [Next.js 13.4.5](https://github.com/vercel/next.js/releases/tag/v13.4.5) webpack has top level await support enabled by default. Similarly Turbopack supports top level await by default as well. TLDR: You can remove `topLevelAwait: true` from the webpack configuration. In writing these tests I found that client components are missing some kind of handling for top level await (async modules) so I've raised that to @gnoff who is going to have a look. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # --> Closes NEXT-3126 Fixes https://github.com/vercel/next.js/issues/43382
2024-04-17 17:44:40 +02:00
test/e2e/async-modules/amp-validator-wasm.js
Reference in a new issue Copy permalink