refactor: better import path alias

[AnsonH]

Description

This commit introduced a new way to specify the import path:

import { Config } from "types"

In the above example, it imports from the types/ folder. However, an issue with this style of import is that it's easy to mistake "types" as the name of a 3rd party dependency

Solution

Try with this: "~/types", "~/components"

• Next.js Docs: https://nextjs.org/docs/advanced-features/module-path-aliases
• Blog article: https://haseebmajid.dev/blog/better-imports-with-babel-tspath