Next.js: Internal Server Error (500) right after installing and running Next.js 9.5.2

Created on 25 Aug 2020  ·  20Comments  ·  Source: vercel/next.js

Bug report

Internal Server Error, Next.js 9.5.2

Describe the bug

Next.js build 9.5.2 is giving Internal Server Error (500) right after installing npx create-next-app

To Reproduce

  1. npx create-next-app
  2. npm run dev
  3. Open the browser localhost:3000
  4. See "Internal Server Error"

Link

https://github.com/janproz/next.js-internal-server-error.git

Expected behavior

Normally, Next.js should output a welcome page.

System information

  • Windows 10
  • Chrome
  • Next.js 9.5.2
  • Node.js 12.18.2
  • React 16.13.1
  • React-DOM 16.13.1
good first issue
Source
picture janproz

Most helpful comment

I can't reproduce it with your steps, also cloned your repo and run npm i && npm run dev, it works for me

picture wong2 on 26 Aug 2020
👍2 🎉1

All 20 comments

Please add a complete reproduction.

timneutkens picture timneutkens on 25 Aug 2020

Kindly check this repository where the last state of the app was uploaded, you can clone it.

https://github.com/janproz/next.js-internal-server-error.git

Next.js 9.3.5 is ok but this Next.js 9.5.2 is giving error out of the box.

thank you.

janproz picture janproz on 25 Aug 2020

I can't reproduce it with your steps, also cloned your repo and run npm i && npm run dev, it works for me

wong2 picture wong2 on 26 Aug 2020
👍2 🎉1

  1. git clone https://github.com/janproz/next.js-internal-server-error

  2. npm install

  3. npm run dev

  4. see "internal server error"

or you can do directly with

  1. npx create-next-app my-app

  2. cd my-app

  3. npm run dev

  4. localhost:3000, see "internal server error"

janproz picture janproz on 26 Aug 2020

Can't reproduce on

  • Mac Catalina
  • Chrome
  • Next.js 9.5.2
  • Node.js 12.18.3
  • React 16.13.1
  • React-DOM 16.13.1
weichienhung picture weichienhung on 26 Aug 2020

is this an isolated case for my machine? I can run Next.js 9.3.5 but Next.js 9.5.2 has problem..

janproz picture janproz on 26 Aug 2020

I'm am having the same issue. Here is my config:

Windows 10 (version 2004 - OS Build 19041.450)
Any Browser
Next.js 9.5.2
Node.js 14.8.0
React 16.13.1
React-DOM 16.13.1

Steps to reproduce 

d:\projects> npx create-next-app --example blog-starter blog-starter-app
d:\projects> cd blog-starter-app
d:\projects\blog-start-app> yarn dev

before I open the browser...

yarn run v1.21.1
warning package.json: No license field
$ next
ready - started server on http://localhost:3000
error - d:/Users/Ken/Source/react/blog-starter-app/pages/_app.js 5:4
Module parse failed: Unexpected token (5:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| export default function MyApp({ Component, pageProps }) {
|   return (
>     <Component {...pageProps} />
|   )
| }

open browser to localhost:3000, see "Internal Server Error", more console messages...

event - build page: /next/dist/pages/_error
wait  - compiling...
error - d:/Users/Ken/Source/react/blog-starter-app/pages/_app.js 5:4
Module parse failed: Unexpected token (5:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| export default function MyApp({ Component, pageProps }) {
|   return (
>     <Component {...pageProps} />
|   )
| }
Error: Cannot find module 'C:\Users\Ken\Source\react\blog-starter-app\.next\server\pages-manifest.json'
Require stack:
- d:\Users\Ken\Source\react\blog-starter-app\node_modules\next\dist\next-server\server\require.js
- d:\Users\Ken\Source\react\blog-starter-app\node_modules\next\dist\next-server\server\load-components.js
- d:\Users\Ken\Source\react\blog-starter-app\node_modules\next\dist\next-server\server\api-utils.js
- d:\Users\Ken\Source\react\blog-starter-app\node_modules\next\dist\next-server\server\next-server.js
- d:\Users\Ken\Source\react\blog-starter-app\node_modules\next\dist\server\next.js
- d:\Users\Ken\Source\react\blog-starter-app\node_modules\next\dist\server\lib\start-server.js
- d:\Users\Ken\Source\react\blog-starter-app\node_modules\next\dist\cli\next-dev.js
- d:\Users\Ken\Source\react\blog-starter-app\node_modules\next\dist\bin\next
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:1080:15)
    at Function.Module._load (internal/modules/cjs/loader.js:923:27)
    at Module.require (internal/modules/cjs/loader.js:1140:19)
    at require (internal/modules/cjs/helpers.js:75:18)
    at getPagePath (d:\Users\Ken\Source\react\blog-starter-app\node_modules\next\dist\next-server\server\require.js:1:657)
    at requirePage (d:\Users\Ken\Source\react\blog-starter-app\node_modules\next\dist\next-server\server\require.js:2:227)
    at loadComponents (d:\Users\Ken\Source\react\blog-starter-app\node_modules\next\dist\next-server\server\load-components.js:1:628)
    at DevServer.findPageComponents (d:\Users\Ken\Source\react\blog-starter-app\node_modules\next\dist\next-server\server\next-server.js:57:189)
    at DevServer.renderErrorToHTML (d:\Users\Ken\Source\react\blog-starter-app\node_modules\next\dist\next-server\server\next-server.js:101:114)
    at DevServer.renderErrorToHTML (d:\Users\Ken\Source\react\blog-starter-app\node_modules\next\dist\server\next-dev-server.js:30:974)
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    'd:\\Users\\Ken\\Source\\react\\blog-starter-app\\node_modules\\next\\dist\\next-server\\server\\require.js',
    'd:\\Users\\Ken\\Source\\react\\blog-starter-app\\node_modules\\next\\dist\\next-server\\server\\load-components.js',
    'd:\\Users\\Ken\\Source\\react\\blog-starter-app\\node_modules\\next\\dist\\next-server\\server\\api-utils.js',
    'd:\\Users\\Ken\\Source\\react\\blog-starter-app\\node_modules\\next\\dist\\next-server\\server\\next-server.js',
    'd:\\Users\\Ken\\Source\\react\\blog-starter-app\\node_modules\\next\\dist\\server\\next.js',
    'd:\\Users\\Ken\\Source\\react\\blog-starter-app\\node_modules\\next\\dist\\server\\lib\\start-server.js',
    'd:\\Users\\Ken\\Source\\react\\blog-starter-app\\node_modules\\next\\dist\\cli\\next-dev.js',
    'd:\\Users\\Ken\\Source\\react\\blog-starter-app\\node_modules\\next\\dist\\bin\\next'
  ]
}
error - d:/Users/Ken/Source/react/blog-starter-app/pages/_app.js 5:4
Module parse failed: Unexpected token (5:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| export default function MyApp({ Component, pageProps }) {
|   return (
>     <Component {...pageProps} />
|   )
| }

Using yarn add [email protected] or any version between that and 9.5.2 does not solve the problem. I was able to run the application before I updated to the latest version of Windows 10. I don't really want to roll back my windows version to test the application. I may configure a docker container to see if that works.

kenssamson picture kenssamson on 27 Aug 2020

@kenssamson Ran fine with Windows 10 10.0.19041 (Build 19041) and Node.js 14.8.0
(Using npm though)

MikeyAlmighty picture MikeyAlmighty on 27 Aug 2020

@MikeyAlmighty Not sure what to say, npm did not work for me either. I'm not familiar with the inner working of Next but it seems have something to do with the loader internal/modules/cjs/loader.js

I was able to get it to work using a docker. I'm still adjusting the docker file settings but I can share them when I'm done. The nice thing about them is that they are not dependent on the actual project and can be used with any Next project.

kenssamson picture kenssamson on 27 Aug 2020
👍1

There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\nonIterableRest.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\slicedToArray.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\nonIterableRest.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\slicedToArray.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/@babel/runtime/helpers/nonIterableSpread.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\nonIterableSpread.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\toConsumableArray.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\nonIterableSpread.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\toConsumableArray.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/@babel/runtime/helpers/possibleConstructorReturn.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\possibleConstructorReturn.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\pages_error.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\possibleConstructorReturn.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\index.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/@babel/runtime/helpers/setPrototypeOf.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\setPrototypeOf.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\construct.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\setPrototypeOf.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\inherits.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/@babel/runtime/helpers/slicedToArray.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\slicedToArray.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\slicedToArray.js
    Used by 5 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\index.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/@babel/runtime/helpers/toConsumableArray.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\toConsumableArray.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\side-effect.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\toConsumableArray.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\dev\error-overlay\format-webpack-messages.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/@babel/runtime/helpers/typeof.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\typeof.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\interopRequireWildcard.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\typeof.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\interopRequireWildcard.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/@babel/runtime/helpers/unsupportedIterableToArray.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\unsupportedIterableToArray.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\slicedToArray.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\unsupportedIterableToArray.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\slicedToArray.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/@babel/runtime/regenerator/index.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\regenerator\index.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\regenerator\index.js
    Used by 5 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\dev\amp-dev.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/next/dist/client/normalize-trailing-slash.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\client\normalize-trailing-slash.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js
  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\normalize-trailing-slash.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/next/dist/client/router.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\client\router.js
    Used by 4 module(s), i. e.
    multi next-client-pages-loader?page=%2F_app&absolutePagePath=private-next-pages%2F_app.js! C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\client\router.js
  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\router.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\dev\prerender-indicator.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/next/dist/client/with-router.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\client\with-router.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\client\router.js
  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\with-router.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\router.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/next/dist/next-server/lib/head-manager-context.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\head-manager-context.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\head.js
  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\next-server\lib\head-manager-context.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\index.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/next/dist/next-server/lib/mitt.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\mitt.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js
  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\next-server\lib\mitt.js
    Used by 3 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\index.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/next/dist/next-server/lib/router-context.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router-context.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\client\router.js
  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\next-server\lib\router-context.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\index.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/next/dist/next-server/lib/router/router.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\client\router.js
  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js
    Used by 3 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\index.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/next/dist/next-server/lib/router/utils/format-url.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\utils\format-url.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\utils.js
  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\utils\format-url.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\next-server\lib\utils.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/next/dist/next-server/lib/router/utils/is-dynamic.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\utils\is-dynamic.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js
  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\utils\is-dynamic.js
    Used by 3 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\index.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/next/dist/next-server/lib/router/utils/parse-relative-url.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\utils\parse-relative-url.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js
  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\utils\parse-relative-url.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/next/dist/next-server/lib/router/utils/querystring.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\utils\querystring.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js
  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\utils\querystring.js
    Used by 4 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\index.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/next/dist/next-server/lib/router/utils/route-matcher.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\utils\route-matcher.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js
  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\utils\route-matcher.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/next/dist/next-server/lib/router/utils/route-regex.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\utils\route-regex.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js
  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\utils\route-regex.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/next/dist/next-server/lib/utils.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\utils.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js
  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\next-server\lib\utils.js
    Used by 3 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\index.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/prop-types/checkPropTypes.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\prop-types\checkPropTypes.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\react\cjs\react.development.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\prop-types\checkPropTypes.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\react\cjs\react.development.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/prop-types/lib/ReactPropTypesSecret.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\prop-types\lib\ReactPropTypesSecret.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\prop-types\checkPropTypes.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\prop-types\lib\ReactPropTypesSecret.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\prop-types\checkPropTypes.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/react-is/cjs/react-is.development.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\react-is\cjs\react-is.development.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\react-is\index.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\react-is\cjs\react-is.development.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\react-is\index.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/react-is/index.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\react-is\index.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\react-is\index.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\index.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/react/cjs/react.development.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\react\cjs\react.development.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\react\index.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\react\cjs\react.development.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\react\index.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/react/index.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\react\index.js
    Used by 9 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\client\router.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\react\index.js
    Used by 29 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\index.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/regenerator-runtime/runtime.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\regenerator-runtime\runtime.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\regenerator\index.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\regenerator-runtime\runtime.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\regenerator\index.js

(webpack)/buildin/global.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\webpack\buildin\global.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\polyfills\polyfill-nomodule.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\webpack\buildin\global.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\platform\platform.js

(webpack)/buildin/module.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\webpack\buildin\module.js
    Used by 21 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\client\polyfills.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\webpack\buildin\module.js
    Used by 37 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\next-dev.js
    info - ready on http://localhost:3000
    event - build page: /next/dist/pages/_error
    wait - compiling...
    event - build page: /next/dist/pages/_error
    warn - C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/@babel/runtime/helpers/arrayLikeToArray.js
    There are multiple modules with names that only differ in casing.
    This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
    Use equal casing. Compare these module identifiers:
  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\arrayLikeToArray.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\unsupportedIterableToArray.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\arrayLikeToArray.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\unsupportedIterableToArray.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/@babel/runtime/helpers/arrayWithHoles.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\arrayWithHoles.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\slicedToArray.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\arrayWithHoles.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\slicedToArray.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/@babel/runtime/helpers/arrayWithoutHoles.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\arrayWithoutHoles.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\toConsumableArray.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\arrayWithoutHoles.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\toConsumableArray.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/@babel/runtime/helpers/assertThisInitialized.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\assertThisInitialized.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\possibleConstructorReturn.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\assertThisInitialized.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\possibleConstructorReturn.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/@babel/runtime/helpers/asyncToGenerator.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\asyncToGenerator.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\asyncToGenerator.js
    Used by 5 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\dev\amp-dev.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/@babel/runtime/helpers/classCallCheck.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\classCallCheck.js
    Used by 3 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\classCallCheck.js
    Used by 3 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\index.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/@babel/runtime/helpers/construct.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\construct.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\client\router.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\construct.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\router.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/@babel/runtime/helpers/createClass.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\createClass.js
    Used by 3 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\createClass.js
    Used by 3 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\index.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/@babel/runtime/helpers/getPrototypeOf.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\getPrototypeOf.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\pages_error.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\getPrototypeOf.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\index.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/@babel/runtime/helpers/inherits.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\inherits.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\pages_error.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\inherits.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\index.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/@babel/runtime/helpers/interopRequireDefault.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\interopRequireDefault.js
    Used by 3 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\client\router.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\interopRequireDefault.js
    Used by 12 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\next-dev.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/@babel/runtime/helpers/interopRequireWildcard.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\interopRequireWildcard.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\client\router.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\interopRequireWildcard.js
    Used by 5 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\next-dev.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/@babel/runtime/helpers/isNativeReflectConstruct.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\isNativeReflectConstruct.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\construct.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\isNativeReflectConstruct.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\construct.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/@babel/runtime/helpers/iterableToArray.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\iterableToArray.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\toConsumableArray.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\iterableToArray.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\toConsumableArray.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/@babel/runtime/helpers/iterableToArrayLimit.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\iterableToArrayLimit.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\slicedToArray.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\iterableToArrayLimit.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\slicedToArray.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/@babel/runtime/helpers/nonIterableRest.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\nonIterableRest.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\slicedToArray.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\nonIterableRest.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\slicedToArray.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/@babel/runtime/helpers/nonIterableSpread.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\nonIterableSpread.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\toConsumableArray.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\nonIterableSpread.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\toConsumableArray.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/@babel/runtime/helpers/possibleConstructorReturn.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\possibleConstructorReturn.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\pages_error.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\possibleConstructorReturn.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\index.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/@babel/runtime/helpers/setPrototypeOf.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\setPrototypeOf.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\construct.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\setPrototypeOf.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\inherits.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/@babel/runtime/helpers/slicedToArray.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\slicedToArray.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\slicedToArray.js
    Used by 5 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\index.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/@babel/runtime/helpers/toConsumableArray.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\toConsumableArray.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\side-effect.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\toConsumableArray.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\dev\error-overlay\format-webpack-messages.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/@babel/runtime/helpers/typeof.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\typeof.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\interopRequireWildcard.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\typeof.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\interopRequireWildcard.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/@babel/runtime/helpers/unsupportedIterableToArray.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\unsupportedIterableToArray.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\helpers\slicedToArray.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\unsupportedIterableToArray.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\helpers\slicedToArray.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/@babel/runtime/regenerator/index.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\regenerator\index.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\regenerator\index.js
    Used by 5 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\dev\amp-dev.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/next/dist/client/normalize-trailing-slash.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\client\normalize-trailing-slash.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js
  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\normalize-trailing-slash.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/next/dist/client/router.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\client\router.js
    Used by 4 module(s), i. e.
    multi next-client-pages-loader?page=%2F_app&absolutePagePath=private-next-pages%2F_app.js! C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\client\router.js
  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\router.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\dev\prerender-indicator.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/next/dist/client/with-router.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\client\with-router.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\client\router.js
  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\with-router.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\router.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/next/dist/next-server/lib/head-manager-context.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\head-manager-context.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\head.js
  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\next-server\lib\head-manager-context.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\index.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/next/dist/next-server/lib/mitt.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\mitt.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js
  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\next-server\lib\mitt.js
    Used by 3 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\index.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/next/dist/next-server/lib/router-context.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router-context.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\client\router.js
  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\next-server\lib\router-context.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\index.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/next/dist/next-server/lib/router/router.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\client\router.js
  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js
    Used by 3 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\index.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/next/dist/next-server/lib/router/utils/format-url.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\utils\format-url.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\utils.js
  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\utils\format-url.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\next-server\lib\utils.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/next/dist/next-server/lib/router/utils/is-dynamic.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\utils\is-dynamic.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js
  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\utils\is-dynamic.js
    Used by 3 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\index.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/next/dist/next-server/lib/router/utils/parse-relative-url.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\utils\parse-relative-url.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js
  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\utils\parse-relative-url.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/next/dist/next-server/lib/router/utils/querystring.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\utils\querystring.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js
  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\utils\querystring.js
    Used by 4 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\index.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/next/dist/next-server/lib/router/utils/route-matcher.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\utils\route-matcher.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js
  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\utils\route-matcher.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/next/dist/next-server/lib/router/utils/route-regex.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\utils\route-regex.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js
  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\utils\route-regex.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/next/dist/next-server/lib/utils.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\utils.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js
  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\next-server\lib\utils.js
    Used by 3 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\index.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/prop-types/checkPropTypes.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\prop-types\checkPropTypes.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\react\cjs\react.development.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\prop-types\checkPropTypes.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\react\cjs\react.development.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/prop-types/lib/ReactPropTypesSecret.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\prop-types\lib\ReactPropTypesSecret.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\prop-types\checkPropTypes.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\prop-types\lib\ReactPropTypesSecret.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\prop-types\checkPropTypes.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/react-is/cjs/react-is.development.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\react-is\cjs\react-is.development.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\react-is\index.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\react-is\cjs\react-is.development.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\react-is\index.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/react-is/index.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\react-is\index.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\lib\router\router.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\react-is\index.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\index.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/react/cjs/react.development.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\react\cjs\react.development.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\react\index.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\react\cjs\react.development.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\react\index.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/react/index.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\react\index.js
    Used by 9 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\client\router.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\react\index.js
    Used by 29 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\index.js

C:/Users/surface/OneDrive/Desktop/ground test/newapp/node_modules/regenerator-runtime/runtime.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\regenerator-runtime\runtime.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@babel\runtime\regenerator\index.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\regenerator-runtime\runtime.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\@babel\runtime\regenerator\index.js

(webpack)/buildin/global.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\webpack\buildin\global.js
    Used by 1 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\polyfills\polyfill-nomodule.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\webpack\buildin\global.js
    Used by 2 module(s), i. e.
    C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\platform\platform.js

(webpack)/buildin/module.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\webpack\buildin\module.js
    Used by 21 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\client\polyfills.js
  • C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\webpack\buildin\module.js
    Used by 37 module(s), i. e.
    C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\@next\react-refresh-utils\loader.js!C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\build\webpack\loaders\next-babel-loader.js??ref--4-1!C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\next\dist\client\next-dev.js
    info - ready on http://localhost:3000
    Error: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
  • You might have mismatching versions of React and the renderer (such as React DOM)
  • You might be breaking the Rules of Hooks
  • You might have more than one copy of React in the same app
    See https://fb.me/react-invalid-hook-call for tips about how to debug and fix this problem.
    at resolveDispatcher (C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\react\cjs\react.development.js:1465:13)
    at useContext (C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\react\cjs\react.development.js:1473:20)
    at Html (C:\Users\surface\OneDrive\desktop\ground test\newapp.next\server\pages_document.js:305:29)
    at processChild (C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\react-dom\cjs\react-dom-server.node.development.js:3043:14)
    at resolve (C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\react-dom\cjs\react-dom-server.node.development.js:2960:5)
    at ReactDOMServerRenderer.render (C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\react-dom\cjs\react-dom-server.node.development.js:3435:22)
    at ReactDOMServerRenderer.read (C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\react-dom\cjs\react-dom-server.node.development.js:3373:29)
    at renderToStaticMarkup (C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\react-dom\cjs\react-dom-server.node.development.js:4004:27)
    at renderDocument (C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\server\render.js:3:624)
    at renderToHTML (C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\server\render.js:50:72)
    Error: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
  • You might have mismatching versions of React and the renderer (such as React DOM)
  • You might be breaking the Rules of Hooks
  • You might have more than one copy of React in the same app
    See https://fb.me/react-invalid-hook-call for tips about how to debug and fix this problem.
    at resolveDispatcher (C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\react\cjs\react.development.js:1465:13)
    at useContext (C:\Users\surface\OneDrive\desktop\ground test\newappnode_modules\react\cjs\react.development.js:1473:20)
    at Html (C:\Users\surface\OneDrive\desktop\ground test\newapp.next\server\pages_document.js:305:29)
    at processChild (C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\react-dom\cjs\react-dom-server.node.development.js:3043:14)
    at resolve (C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\react-dom\cjs\react-dom-server.node.development.js:2960:5)
    at ReactDOMServerRenderer.render (C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\react-dom\cjs\react-dom-server.node.development.js:3435:22)
    at ReactDOMServerRenderer.read (C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\react-dom\cjs\react-dom-server.node.development.js:3373:29)
    at renderToStaticMarkup (C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\react-dom\cjs\react-dom-server.node.development.js:4004:27)
    at renderDocument (C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\server\render.js:3:624)
    at renderToHTML (C:\Users\surface\OneDrive\Desktop\ground test\newappnode_modules\next\dist\next-server\server\render.js:50:72)
janproz picture janproz on 28 Aug 2020

Bump. I am also having this problem.

DannyRoberts95 picture DannyRoberts95 on 28 Aug 2020

Can't reproduce on:

  • MacOS Catalina 10.15.6
  • Next.js 9.5.2
  • Node.js 12.17.0
  • React 16.13.1
  • React-DOM 16.13.1
vipul0092 picture vipul0092 on 29 Aug 2020

Also having similar problem with create-next-app, with a bit different error on server side (TypeError: input.module.originalSource is not a function and Module not found: Can't resolve './client/polyfills.js')

Relevant parts of console log of commands for versions and steps to reproduce:

❯ system_profiler SPSoftwareDataType|grep "System Version"
      System Version: macOS 10.14.6 (18G6020)

❯ npx -v && node -v
6.14.4
v12.16.2

❯ npx create-next-app my-app
npx: installed 1 in 0.723s
Creating a new Next.js app in /Users/mpe/work/my-app.

Installing react, react-dom, and next using yarn...

yarn add v1.22.4
info No lockfile found.
[1/4] 🔍  Resolving packages...
warning next > [email protected]: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
warning next > [email protected]: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning next > chokidar > [email protected]: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
warning next > webpack > watchpack > watchpack-chokidar2 > [email protected]: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
warning next > resolve-url-loader > rework > css > [email protected]: Please see https://github.com/lydell/urix#deprecated
warning next > chokidar > braces > snapdragon > source-map-resolve > [email protected]: Please see https://github.com/lydell/urix#deprecated
warning next > chokidar > braces > snapdragon > source-map-resolve > [email protected]: https://github.com/lydell/resolve-url#deprecated
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
[4/4] 🔨  Building fresh packages...
success Saved lockfile.
success Saved 401 new dependencies.
info Direct dependencies
├─ [email protected]
├─ [email protected]
└─ [email protected]
info All dependencies

...<redacted>...

✨  Done in 8.47s.

Initialized a git repository.

Success! Created my-app at /Users/mpe/work/my-app
Inside that directory, you can run several commands:

  yarn dev
    Starts the development server.

  yarn build
    Builds the app for production.

  yarn start
    Runs the built app in production mode.

We suggest that you begin by typing:

  cd my-app
  yarn dev

❯ cd my-app

❯ yarn dev
yarn run v1.22.4
$ next dev
ready - started server on http://localhost:3000
TypeError: input.module.originalSource is not a function
    at getNotFoundError (/Users/mpe/work/my-app/node_modules/next/dist/build/webpack/plugins/wellknown-errors-plugin/parseNotFoundError.js:1:644)
    at getModuleBuildError (/Users/mpe/work/my-app/node_modules/next/dist/build/webpack/plugins/wellknown-errors-plugin/webpackModuleError.js:1:2631)
    at /Users/mpe/work/my-app/node_modules/next/dist/build/webpack/plugins/wellknown-errors-plugin/index.js:1:599
    at Array.map (<anonymous>)
    at /Users/mpe/work/my-app/node_modules/next/dist/build/webpack/plugins/wellknown-errors-plugin/index.js:1:513
    at AsyncSeriesHook.eval [as callAsync] (eval at create (/Users/mpe/work/my-app/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:17)
    at AsyncSeriesHook.lazyCompileHook (/Users/mpe/work/my-app/node_modules/tapable/lib/Hook.js:154:20)
    at /Users/mpe/work/my-app/node_modules/webpack/lib/Compilation.js:1423:35
    at AsyncSeriesHook.eval [as callAsync] (eval at create (/Users/mpe/work/my-app/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:4:1)
    at AsyncSeriesHook.lazyCompileHook (/Users/mpe/work/my-app/node_modules/tapable/lib/Hook.js:154:20)
error - multi ./client/polyfills.js ./node_modules/next/dist/client/next-dev.js
Module not found: Can't resolve './client/polyfills.js' in '/Users/mpe/work/my-app'
mpeltonen picture mpeltonen on 9 Sep 2020

I got the same error when installing package using pnpm & then when using yarn it run good. Only with the nextjs-blog example.
Work fine with the original template of create-next-app using pnpx

bawdeveloppement picture bawdeveloppement on 19 Sep 2020

I was facing the same issue. "Internal Server Error" while creating the app from scratch . Tried using different versions of node react and react-dom, repeated the same process with yarn but got same internal error.

What worked for me:
I changed the project directory. Followed the same process again without any change and voila! Worked like magic. All errors gone, even warnings too.

devspectre91 picture devspectre91 on 21 Oct 2020
👍1

Please follow this URL to make sure to use the correct Node version,

I've switched to Node 12.18.1 by nvm use 12.18.0 then 'npm Install' and 'npm run dev.'

Tip: remove node folder, and package-lock.json helps a lot.

najandz picture najandz on 30 Oct 2020
👍1

For me, the root cause for this problem was that I had accidentally copied and then forgotten extra next.config.js file in one of the parent directories of the create-next-app project directory. So check out that you don't have extra config file lying around upper in the directory hierarchy if you're experiencing this issue.

mpeltonen picture mpeltonen on 3 Nov 2020
👍1

I also experienced this with a fresh app created using create-next-app - Next 10.0.1 running on Windows on Node 14.15.0 and yarn 1.22.4.

The trigger seems to be if the project is running from a path with the CWD set to that directory in a different case. Remember that on Windows the filesystem is case-insensitive by default.

Repro (Windows PowerShell)

mkdir c:\src\UC    #NOTE UC upper case
cd \src\uc       # NOTE uc lower case
npx create-next-app test
cd test
yarn dev

Output:

yarn run v1.22.4
$ next dev
ready - started server on http://localhost:3000
node.exe : warn  - C:/src/UC/test/node_modules/@babel/runtime/helpers/arrayLikeToArray.js

There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:
* C:\src\UC\test\node_modules\@babel\runtime\helpers\arrayLikeToArray.js
    Used by 2 module(s), i. e.
    C:\src\UC\test\node_modules\@babel\runtime\helpers\unsupportedIterableToArray.js
* C:\src\uc\test\node_modules\@babel\runtime\helpers\arrayLikeToArray.js
    Used by 2 module(s), i. e.
    C:\src\uc\test\node_modules\@babel\runtime\helpers\unsupportedIterableToArray.js

<REPEATED FOR MANY MODULES>

Error: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for 
one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.
    at resolveDispatcher (C:\src\uc\test\.next\server\pages\_document.js:3379:13)
    at useContext (C:\src\uc\test\.next\server\pages\_document.js:3387:20)
    at Html (C:\src\uc\test\.next\server\pages\_document.js:330:29)
    at processChild (C:\src\UC\test\node_modules\react-dom\cjs\react-dom-server.node.development.js:3353:14)
    at resolve (C:\src\UC\test\node_modules\react-dom\cjs\react-dom-server.node.development.js:3270:5)
    at ReactDOMServerRenderer.render 
(C:\src\UC\test\node_modules\react-dom\cjs\react-dom-server.node.development.js:3753:22)
    at ReactDOMServerRenderer.read 
(C:\src\UC\test\node_modules\react-dom\cjs\react-dom-server.node.development.js:3690:29)
    at renderToStaticMarkup (C:\src\UC\test\node_modules\react-dom\cjs\react-dom-server.node.development.js:4314:27)
    at renderDocument (C:\src\UC\test\node_modules\next\dist\next-server\server\render.js:3:669)
    at renderToHTML (C:\src\UC\test\node_modules\next\dist\next-server\server\render.js:52:103)

The workaround is to fix the CWD so that is has the casing matching the actual directory - known as the canonical path (continuing from above)

cd \src\UC\test     #NOTE upper case UC matching what we mkdired

Output:

PS C:\src\UC\test> yarn dev
yarn run v1.22.4
$ next dev
ready - started server on http://localhost:3000
event - compiled successfully
event - build page: /
wait  - compiling...
event - compiled successfully

Note that it's more difficult to reproduce this outside of Windows Powershell as CMD sets the working directory to the correct canonical path if you use cd within a session.

I would guess that this is actually an issue with something lower-level like Webpack or one of it's loaders plugins, but maybe Next can add a workaround to set the CWD to the canonical path when invoking it.

rnwood picture rnwood on 7 Nov 2020

Having the same issue on
Node.JS - v14.4.0.
npm - v6.14.5
react - v16.13.1
react-dom - v16.13.1
ubuntu - 20.04.1 LTS
next.JS - 10.0.1
I will troubleshoot later, and try some of the above suggestions.

jswelsh picture jswelsh on 16 Nov 2020
👀1

Same experience here on Windows. I created a new nextjs app with npx create-next-app from the new powershell terminal (pwsh). After reading @rnwood comment I tried switching from powershell to the old command terminal and now it build.

BjornFridal picture BjornFridal on 17 Nov 2020
Was this page helpful?
0 / 5 - 0 ratings

Related issues

jesselee34 picture jesselee34  ·  3Comments
ghost picture ghost  ·  3Comments
kenji4569 picture kenji4569  ·  3Comments
flybayer picture flybayer  ·  3Comments
formula349 picture formula349  ·  3Comments