new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Next.js App Router · all subjects

getting-started/module-paths

4 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Absolute imports and path aliases in Next.js

Next.js has built-in support for the `baseUrl` and `paths` options in `tsconfig.json` or `jsconfig.json`. These allow you to alias project directories to absolute paths, making imports cleaner. For example, instead of `import { Button } from '../../../components/button'`, you can write `import { Button } from '@/components/button'`.

Configure baseUrl for absolute imports

To configure absolute imports, add the `baseUrl` option to `tsconfig.json` or `jsconfig.json`: ```json { "compilerOptions": { "baseUrl": "src/" } } ```

Configure path aliases with baseUrl

To create path aliases, use the `paths` option in `tsconfig.json` or `jsconfig.json` along with `baseUrl`. Each path is relative to the baseUrl location: ```json { "compilerOptions": { "baseUrl": "src/", "paths": { "@/styles/*": ["styles/*"], "@/components/*": ["components/*"] } } } ```

Import Aliases purpose and benefit

Import Aliases are custom path mappings that provide shorthand references for frequently used directories. Import aliases reduce the complexity of relative imports and make code more readable and maintainable.

Give your agent this brain