Are you tired of writing lengthy import paths like "../../../components/ui/test" in your Next.js projects? Well, rejoice because there's a solution that can streamline your imports and make your code much cleaner. Enter path aliases.

In Next.js, path aliases allow you to define custom shortcuts for your import paths, making them more concise and readable. Instead of navigating through multiple directories to import a component, you can simply use a defined alias**.**

Setting it Up

Update tsconfig.json: Open your project's tsconfig.json file and add the "paths" property if it doesn't already exist. This property allows you to define your custom path aliases.

{
  "compilerOptions": {
    "baseUrl": ".",
    "paths": {
      "@/*": ["components/*"]
    }
  }
}

{
  "compilerOptions": {
    "baseUrl": ".",
    "paths": {
      "@/*": ["components/*"]
    }
  }
}

In this example, we've defined an alias "@" that points to the "components" directory. You can customize this alias and directory path according to your project structure.

Utilize the Alias: Now, instead of writing lengthy import paths, you can use your defined alias. For instance, instead of:

import { Component } from '../../../components/ui/test';

import { Component } from '../../../components/ui/test';

You can now simply write:

import { Component } from '@/components/ui/test';

import { Component } from '@/components/ui/test';

By chaining the alias "@" followed by the relative path, you immediately make your imports more concise and easier to understand.

After making changes to tsconfig.json, don't forget to restart your development server for the changes to take effect.

And that's it! By incorporating custom path aliases into your Next.js projects, you can significantly enhance code readability and maintainability. So go ahead, simplify your imports, and focus more on building awesome features for your Next.js applications.