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

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

50 lines
1.8 KiB
Text
Raw Normal View History

fix snapshots broken by prettier (also fix .prettierignore) (#48586) ### What? Fix snapshots that were no longer fulfilling the original purpose after prettier had its way. The `.prettierignore` also had the old `target/` directory (prior to the `Cargo.toml` move in #48198) so running `pnpm prettier-fix` formatted files in the `target/` directory
2023-04-21 20:52:08 +02:00
# Build artifacts
.next/
.turbo/
_next/
__tmp__/
dist/
target/
compiled/
lerna.json
test-timings.json
pnpm-lock.yaml
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
fix snapshots broken by prettier (also fix .prettierignore) (#48586) ### What? Fix snapshots that were no longer fulfilling the original purpose after prettier had its way. The `.prettierignore` also had the old `target/` directory (prior to the `Cargo.toml` move in #48198) so running `pnpm prettier-fix` formatted files in the `target/` directory
2023-04-21 20:52:08 +02:00
Move next-codemod to Next.js monorepo (#15536)
2020-08-10 11:14:53 +02:00
.github/actions/next-stats-action/.work
fix snapshots broken by prettier (also fix .prettierignore) (#48586) ### What? Fix snapshots that were no longer fulfilling the original purpose after prettier had its way. The `.prettierignore` also had the old `target/` directory (prior to the `Cargo.toml` move in #48198) so running `pnpm prettier-fix` formatted files in the `target/` directory
2023-04-21 20:52:08 +02:00
prettier fix for `next-swc` (#47873) This enables the existing prettier config to auto apply to code inside the `next-swc` package
2023-04-19 19:44:27 +02:00
packages/next-swc/crates/**/tests/**/output*
fix snapshots broken by prettier (also fix .prettierignore) (#48586) ### What? Fix snapshots that were no longer fulfilling the original purpose after prettier had its way. The `.prettierignore` also had the old `target/` directory (prior to the `Cargo.toml` move in #48198) so running `pnpm prettier-fix` formatted files in the `target/` directory
2023-04-21 20:52:08 +02:00
packages/next-swc/crates/core/tests/loader/issue-32553/input.js
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
# prettier destroys the directives here
fix snapshots broken by prettier (also fix .prettierignore) (#48586) ### What? Fix snapshots that were no longer fulfilling the original purpose after prettier had its way. The `.prettierignore` also had the old `target/` directory (prior to the `Cargo.toml` move in #48198) so running `pnpm prettier-fix` formatted files in the `target/` directory
2023-04-21 20:52:08 +02:00
packages/next-swc/crates/next-custom-transforms/tests/errors/react-server-components/client-graph/use-client/input.js
packages/next-swc/crates/next-custom-transforms/tests/errors/react-server-components/server-graph/fake-client-entry/input.js
packages/next-swc/crates/next-custom-transforms/tests/errors/server-actions/server-graph/8/input.js
packages/next-swc/crates/next-custom-transforms/tests/errors/server-actions/server-graph/9/input.js
packages/next-swc/crates/next-custom-transforms/tests/fixture/optimize-barrel/normal/4/input.js
packages/next-swc/crates/next-custom-transforms/tests/fixture/react-server-components/client-graph/client-entry/input.js
packages/next-swc/crates/next-custom-transforms/tests/fixture/react-server-components/server-graph/client-entry/input.js
Add missing @napi-rs/cli devDependency to next-swc (#39164) Otherwise build-native fails with "napi: command not found.". Alternatively, this is missing from this package's devDependencies. ## Documentation / Examples - [x] Make sure the linting passes by running `pnpm lint` - [x] The examples guidelines are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing.md#adding-examples) P.S.: local copy fails `pnpm lint` due to the `target` subfolder with intermediate rust build artifacts... should I add a `.prettierignore` update to exclude `/packages/next-swc/target/`? Co-authored-by: JJ Kasper <22380829+ijjk@users.noreply.github.com>
2022-07-31 00:08:50 +02:00
packages/next-swc/native/**/*
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/**/*
fix snapshots broken by prettier (also fix .prettierignore) (#48586) ### What? Fix snapshots that were no longer fulfilling the original purpose after prettier had its way. The `.prettierignore` also had the old `target/` directory (prior to the `Cargo.toml` move in #48198) so running `pnpm prettier-fix` formatted files in the `target/` directory
2023-04-21 20:52:08 +02:00
packages/next-codemod/transforms/__testfixtures__/**
packages/next-codemod/transforms/__tests__/**
Move next-codemod to Next.js monorepo (#15536)
2020-08-10 11:14:53 +02:00
packages/next-codemod/**/*.js
packages/next-codemod/**/*.d.ts
fix snapshots broken by prettier (also fix .prettierignore) (#48586) ### What? Fix snapshots that were no longer fulfilling the original purpose after prettier had its way. The `.prettierignore` also had the old `target/` directory (prior to the `Cargo.toml` move in #48198) so running `pnpm prettier-fix` formatted files in the `target/` directory
2023-04-21 20:52:08 +02:00
Update Azure config (#18931)
2020-11-09 06:56:39 +01:00
packages/next-env/**/*.d.ts
fix snapshots broken by prettier (also fix .prettierignore) (#48586) ### What? Fix snapshots that were no longer fulfilling the original purpose after prettier had its way. The `.prettierignore` also had the old `target/` directory (prior to the `Cargo.toml` move in #48198) so running `pnpm prettier-fix` formatted files in the `target/` directory
2023-04-21 20:52:08 +02:00
chore: Set Prettier to ignore test output (#26353) Co-authored-by: JJ Kasper <jj@jjsweb.site>
2021-07-20 21:37:44 +02:00
test/**/out/**
hmr error improvements (#30616) Co-authored-by: Hannes Bornö <hannes.borno@vercel.com> Co-authored-by: Hannes Bornö <borno.hannes@gmail.com>
2023-01-06 20:35:16 +01:00
test/development/basic/hmr/components/parse-error.js
fix snapshots broken by prettier (also fix .prettierignore) (#48586) ### What? Fix snapshots that were no longer fulfilling the original purpose after prettier had its way. The `.prettierignore` also had the old `target/` directory (prior to the `Cargo.toml` move in #48198) so running `pnpm prettier-fix` formatted files in the `target/` directory
2023-04-21 20:52:08 +02:00
Exclude bench/nested-deps from prettier check
2021-10-10 13:20:16 +02:00
bench/nested-deps/pages/**/*
bench/nested-deps/components/**/*
fix snapshots broken by prettier (also fix .prettierignore) (#48586) ### What? Fix snapshots that were no longer fulfilling the original purpose after prettier had its way. The `.prettierignore` also had the old `target/` directory (prior to the `Cargo.toml` move in #48198) so running `pnpm prettier-fix` formatted files in the `target/` directory
2023-04-21 20:52:08 +02:00
Update Convex Example (#39562) This makes a few changes to the Convex example app. We're using this example app in the Convex quick start (https://docs.convex.dev/quick-start), so I want to make sure we're setting new users up for success. Upgrade to the newest version of Convex (includes adding a tsconfig.json for Convex functions) Switch to pinning Convex to latest Check in generated code so the example will make more sense to users browsing on GitHub or before they regenerate the code. This required ignoring it in the global .prettierignore Add prettier Update styling so "Powered by Convex" appears on screen. Switch the syntax of one function to make it type check after developers add a schema Documentation / Examples Make sure the linting passes by running pnpm lint The examples guidelines are followed from our contributing doc Co-authored-by: JJ Kasper <jj@jjsweb.site>
2022-08-16 02:21:53 +02:00
**/convex/_generated/**
Updates prettier to latest version. (#51000) There are some incoming docs / MDX changes where prettier will throw an error when using the older version. Updating prettier before I bring in those changes. Looks like the most notable change is adding parentheses around `typeof` checks in TypeScript. **Before** ``` export type Locale = typeof i18n['locales'][number] ``` **After** ``` export type Locale = (typeof i18n)['locales'][number] ```
2023-06-09 16:58:19 +02:00
**/.tina/__generated__/**
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