e50d22b992
As per https://github.com/vercel/next.js/pull/45670#issuecomment-1428729000, it's very necessary to include `tsconfig.json` in our tests as we need to test specific TS configurations sometimes. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see [`contributing.md`](https://github.com/vercel/next.js/blob/canary/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` - [ ] [e2e](https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) 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`](https://github.com/vercel/next.js/blob/canary/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)
53 lines
537 B
Text
53 lines
537 B
Text
# build output
|
|
dist
|
|
.next
|
|
target
|
|
packages/next/wasm/@next
|
|
packages/*/packed-*.tgz
|
|
|
|
# dependencies
|
|
node_modules
|
|
package-lock.json
|
|
yarn.lock
|
|
!/yarn.lock
|
|
test/node_modules
|
|
.pnpm-store/
|
|
|
|
# logs & pids
|
|
*.log
|
|
pids
|
|
*.cpuprofile
|
|
|
|
# coverage
|
|
.nyc_output
|
|
coverage
|
|
|
|
# test output
|
|
test/**/out*
|
|
test/**/next-env.d.ts
|
|
.DS_Store
|
|
/e2e-tests
|
|
test/tmp/**
|
|
test/.trace
|
|
test/traces
|
|
|
|
# Editors
|
|
**/.idea
|
|
**/.#*
|
|
.nvmrc
|
|
|
|
# examples
|
|
examples/**/out
|
|
examples/**/.env*.local
|
|
|
|
pr-stats.md
|
|
test-timings.json
|
|
|
|
# Vercel
|
|
.vercel
|
|
.now
|
|
|
|
# Cache
|
|
*.tsbuildinfo
|
|
.swc/
|
|
.turbo
|