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

13 lines
338 B
Text
Raw Normal View History

Adjust Commit Linting Hook (#9694)
2019-12-11 03:29:39 +01:00
**/.next/**
**/_next/**
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
**/dist/**
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/**
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
packages/next/compiled/**/*
feat: webpack inlining with configuration for v4 / v5 (#20598)
2021-01-14 02:59:08 +01:00
packages/next/bundles/webpack/packages/*.runtime.js
Do not prettify `lerna.json`
2020-05-04 03:56:17 +02:00
lerna.json
Move next-codemod to Next.js monorepo (#15536)
2020-08-10 11:14:53 +02:00
packages/next-codemod/transforms/__testfixtures__/**/*
packages/next-codemod/transforms/__tests__/**/*
Fix typo `pnpm-lock.yam` in `.prettierignore_staged` (#42212) Fix typo `pnpm-lock.yam` in #38915 Regenerate pnpm-lock.yaml without formatting (#42208) <!-- 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 that you're making: --> ## 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` - [ ] 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) None of the above Co-authored-by: JJ Kasper <jj@jjsweb.site>
2022-10-31 06:58:45 +01:00
pnpm-lock.yaml
chore: check against `npm` version in issue validator (#38915) I did some experimenting to see if we can grab the latest version from npm instead of GitHub releases since that's the version the user can actually use. The npm registry sends the package metadata in a gigantic (~8mb for `next`) JSON response and parsing it with `res.json()` takes several seconds, but using `ReadableStream`, we only care about the first chunk. This way we can grab the relevant version information in a few ms. ~I added `undici` which implements `res.body.getReader()`.~ Using Node 18/native `fetch`.
2022-08-25 18:43:20 +02:00
.github/actions/issue-validator/index.mjs
Fix typo `pnpm-lock.yam` in `.prettierignore_staged` (#42212) Fix typo `pnpm-lock.yam` in #38915 Regenerate pnpm-lock.yaml without formatting (#42208) <!-- 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 that you're making: --> ## 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` - [ ] 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) None of the above Co-authored-by: JJ Kasper <jj@jjsweb.site>
2022-10-31 06:58:45 +01:00
**/convex/_generated/**
Reference in a new issue Copy permalink