2023-10-18 10:59:43 +00:00
|
|
|
---
|
|
|
|
title: Build Tooling
|
|
|
|
description: 'Learn how to migrate from Nuxt 2 to Nuxt 3 build tooling.'
|
|
|
|
---
|
2022-03-30 17:32:30 +00:00
|
|
|
|
|
|
|
We use the following build tools by default:
|
|
|
|
|
2024-12-02 11:35:47 +00:00
|
|
|
- [Vite](https://vite.dev) or [webpack](https://webpack.js.org)
|
2023-10-18 11:26:06 +00:00
|
|
|
- [Rollup](https://rollupjs.org)
|
|
|
|
- [PostCSS](https://postcss.org)
|
|
|
|
- [esbuild](https://esbuild.github.io)
|
2022-03-30 17:32:30 +00:00
|
|
|
|
|
|
|
For this reason, most of your previous `build` configuration in `nuxt.config` will now be ignored, including any custom babel configuration.
|
|
|
|
|
|
|
|
If you need to configure any of Nuxt's build tools, you can do so in your `nuxt.config`, using the new top-level `vite`, `webpack` and `postcss` keys.
|
|
|
|
|
2023-10-18 10:59:43 +00:00
|
|
|
In addition, Nuxt ships with TypeScript support.
|
|
|
|
|
|
|
|
:read-more{to="/docs/guide/concepts/typescript"}
|
2022-03-30 17:32:30 +00:00
|
|
|
|
|
|
|
## Steps
|
|
|
|
|
|
|
|
1. Remove `@nuxt/typescript-build` and `@nuxt/typescript-runtime` from your dependencies and modules.
|
2023-10-18 10:59:43 +00:00
|
|
|
2. Remove any unused babel dependencies from your project.
|
|
|
|
3. Remove any explicit core-js dependencies.
|
|
|
|
4. Migrate `require` to `import`.
|
2022-03-30 17:32:30 +00:00
|
|
|
|
|
|
|
<!-- TODO: Enabling webpack builder -->
|