Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Correct link to Customizing Turbopack #4971

Merged
merged 1 commit into from May 16, 2023
Merged

Correct link to Customizing Turbopack #4971

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/pages/pack/docs/comparisons/webpack.mdx
View file
Open in desktop
Expand Up @@ -63,4 +63,4 @@ In a 1,000 module application, Turbopack can react to file changes **<DocsBenchm

webpack has an extraordinary collection of [plugins](https://webpack.js.org/plugins/) to customize its behavior. Composing plugins lets you create custom toolchains which can support a huge variety of bundler features.

As of Next.js 13.2, Turbopack introduced a compatibility layer to support webpack's loaders and resolve aliases. See [Customizing Turbopack](features/customizing-turbopack) for how to configure them. In the future, we plan to make Turbopack just as extensible as webpack - though likely with an altered API.
As of Next.js 13.2, Turbopack introduced a compatibility layer to support webpack's loaders and resolve aliases. See [Customizing Turbopack](../features/customizing-turbopack) for how to configure them. In the future, we plan to make Turbopack just as extensible as webpack - though likely with an altered API.