06d60ac140
### What? Refactors the resolving logic for the `app` loader tree. This PR ensures it's used to create entrypoints in turbopack. Next up is integrating it into the webpack build too. These changes also ensure that parallel routes resolving is applied, which previously wasn't supported in turbopack. ### Why? Part of the effort to deduplicate critical logic between turbopack/webpack in Next.js, this will help land features in turbopack/webpack at the same time. ### How? Quite a few changes. @sokra helped a ton on this PR. `app_structure.rs` was changed to the new resolving logic so most of the logic is there. Additionally we added support for calling the same function in two ways from Node.js: `turbo.entrypoints.get` and `turbo.entrypoints.getStream`. `get` can be used by `next build` to get the full list of entrypoints/loadertrees once. `getStream` has watching built-in and calls a callback function with the new list anytime a file is added that would change the loadertree. <!-- 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 or adding/fixing 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 # -->
78 lines
2.1 KiB
JSON
78 lines
2.1 KiB
JSON
{
|
|
// Formatting using Prettier by default for all languages
|
|
"editor.defaultFormatter": "esbenp.prettier-vscode",
|
|
// Formatting using Prettier for JavaScript, overrides VSCode default.
|
|
"[javascript]": {
|
|
"editor.defaultFormatter": "esbenp.prettier-vscode"
|
|
},
|
|
// Formatting using Rust-Analyzer for Rust.
|
|
"[rust]": {
|
|
"editor.defaultFormatter": "rust-lang.rust-analyzer"
|
|
},
|
|
// Linting using ESLint.
|
|
"eslint.validate": [
|
|
"javascript",
|
|
"javascriptreact",
|
|
"typescript",
|
|
"typescriptreact"
|
|
],
|
|
// Disable Jest autoRun as otherwise it will start running all tests the first time.
|
|
"jest.autoRun": "off",
|
|
|
|
// Debugging.
|
|
"debug.javascript.unmapMissingSources": true,
|
|
|
|
"files.exclude": {
|
|
"**/node_modules": false,
|
|
"node_modules": true,
|
|
"*[!test]**/node_modules": true
|
|
},
|
|
|
|
// Ensure enough terminal history is preserved when running tests.
|
|
"terminal.integrated.scrollback": 10000,
|
|
|
|
// Configure todo-tree to exclude node_modules, dist, and compiled.
|
|
"todo-tree.filtering.excludeGlobs": [
|
|
"**/node_modules",
|
|
"**/dist",
|
|
"**/compiled"
|
|
],
|
|
// Match TODO-APP in addition to other TODOs.
|
|
"todo-tree.general.tags": [
|
|
"BUG",
|
|
"HACK",
|
|
"FIXME",
|
|
"TODO",
|
|
"XXX",
|
|
"[ ]",
|
|
"[x]",
|
|
"TODO-APP"
|
|
],
|
|
|
|
// Disable TypeScript surveys.
|
|
"typescript.surveys.enabled": false,
|
|
|
|
// Enable file nesting for unit test files.
|
|
"explorer.fileNesting.enabled": true,
|
|
"explorer.fileNesting.patterns": {
|
|
"*.ts": "$(capture).test.ts, $(capture).test.tsx",
|
|
"*.tsx": "$(capture).test.ts, $(capture).test.tsx"
|
|
},
|
|
// Allow to find the cargo project for rust-analyzer.
|
|
"rust-analyzer.linkedProjects": ["packages/next-swc/Cargo.toml"],
|
|
// Compile rust-analyzer in a separate directory to avoid conflicts with the main project.
|
|
"rust-analyzer.checkOnSave.extraEnv": {
|
|
"CARGO_TARGET_DIR": "target/rust-analyzer"
|
|
},
|
|
"rust-analyzer.server.extraEnv": {
|
|
"CARGO_TARGET_DIR": "target/rust-analyzer",
|
|
"RUST_BACKTRACE": "0"
|
|
},
|
|
"cSpell.words": [
|
|
"Entrypoints",
|
|
"napi",
|
|
"opentelemetry",
|
|
"Threadsafe",
|
|
"zipkin"
|
|
]
|
|
}
|