Module not found: Can't resolve '@/components #27666

zhangwei900808 · 2021-08-02T00:08:58Z

zhangwei900808
Aug 2, 2021

I add jsconfig.json

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

but when I run is error

error - ./src/components/context/mainContext/index.js:3:0
Module not found: Can't resolve '@/components/layout/pageHeader/logoInHeader'
  1 | import React, { useState, useEffect } from "react";
  2 | import { useRouter } from "next/router";
> 3 | import LogoInHeader from "@/components/layout/pageHeader/logoInHeader";
  4 | import Menus from "../../navMenus";
  5 | import Record from "../../layout/record";
  6 | import styles from "./index.module.scss";

zhangwei900808 · 2021-08-02T11:44:25Z

zhangwei900808
Aug 2, 2021
Author

who can help me

0 replies

polRk · 2021-08-03T10:29:09Z

polRk
Aug 3, 2021

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

See more: https://stackoverflow.com/questions/43281741/how-to-use-paths-in-tsconfig-json

0 replies

nitinpatelm · 2023-07-25T11:21:59Z

nitinpatelm
Jul 25, 2023

Same problem for me

1 reply

officialkevinbrian Aug 23, 2023

@nitinpatelm did you find solution?

MMTE · 2023-09-24T09:38:48Z

MMTE
Sep 24, 2023

check if paths option is available both in tsconfig.json and jsconfig.json if you are using typescript or javascript.

0 replies

alimukhtar53 · 2023-10-03T01:10:50Z

alimukhtar53
Oct 3, 2023

I had to rename my dir name inside components from stepsInfo to steps-info

My project setup was:

project-root/
├── app/
│ ├── components/
│ │ └── stepsInfo/
│ │ └── Step1.tsx
├── tsconfig.json

Reference

0 replies

AleksaRadovanovic · 2023-10-08T19:10:50Z

AleksaRadovanovic
Oct 8, 2023

You probably renamed folder in components, in my case I renamed components/UI to components/ui.
Git might not recognize this by default. To fix it, run:

git config core.ignorecase false

Then commit and push your changes.

18 replies

tahsinature May 20, 2024

Thanks a lot. Saved my day.
Wasn't expecting this. Didn't know git has case insensitivity too.

artemkamyshenkov Jun 27, 2024

Thank you a lot, bro

IsmaelOmar Jul 4, 2024

I love you

lilsouza Jul 22, 2024

Thank you so much!!!

benderlidze Aug 25, 2024

And you may need to do this after pull


//Clear Next.js build cache
rm -rf .next
//Reinstall node_modules
rm -rf node_modules
npm install
// Rebuild the project
npm run build

fyargat · 2023-10-13T18:20:01Z

fyargat
Oct 13, 2023

// next.config.js
/** @type {import('next').NextConfig} */

const path = require('path');

const nextConfig = {
  webpack: (config) => {
    config.resolve.alias = {
      ...config.resolve.alias,
      '@': path.resolve(__dirname, './'),
    };

    return config;
  },
};

module.exports = nextConfig;

See more: https://stackoverflow.com/questions/76676456/next-js-v13-in-docker-does-not-respect-path-alias-but-works-locally

3 replies

Muskulee Feb 27, 2024

This resolves the issue: You can however use the below in ES6:
import path from 'path';

const __dirname = new URL('.', import.meta.url).pathname;

const nextConfig = {
webpack: (config) => {
config.resolve.alias = {
...config.resolve.alias,
'@': path.resolve(__dirname, './'),
};
return config;
},
};
export default nextConfig;

I hope this helps too!

mmk0612 Jun 2, 2024

This worked for me update the next.Config.mjs file this way

YoSoyPhil Aug 28, 2024

Thank you so much! <3

rajdevkumar2003 · 2024-03-14T06:36:31Z

rajdevkumar2003
Mar 14, 2024

"paths": {
"@/": ["./"]
}

0 replies

rajdevkumar2003 · 2024-05-20T07:58:36Z

rajdevkumar2003
May 20, 2024

👍🏼

…

On Mon, May 20, 2024, 12:44 Bo Kou ***@***.***> wrote: You saved me today. Thanks! — Reply to this email directly, view it on GitHub <#27666 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BARC4ZCPQ7SNYI5CCLYKELTZDGPFZAVCNFSM5BLU5672U5DIOJSWCZC7NNSXTOKENFZWG5LTONUW63SDN5WW2ZLOOQ5TSNBZGMYTCMY> . You are receiving this because you commented.Message ID: <vercel/next. ***@***.***>

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Module not found: Can't resolve '@/components #27666

{{title}}

Replies: 9 comments 22 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Module not found: Can't resolve '@/components #27666

Replies: 9 comments · 22 replies

zhangwei900808 Aug 2, 2021 Author

Replies: 9 comments 22 replies

zhangwei900808
Aug 2, 2021
Author