Console message after running npm run dev
Unanswered
Weevil parasitoid posted this in #help-forum
Weevil parasitoidOP
Does anyone know what's up?
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
> <!doctype html>
| <html>
| <head>
Import trace for requested module:
./node_modules/@mapbox/node-pre-gyp/lib/util/nw-pre-gyp/index.html
./node_modules/@mapbox/node-pre-gyp/lib/ sync ^\.\/.*$
./node_modules/@mapbox/node-pre-gyp/lib/node-pre-gyp.js
./node_modules/bcrypt/bcrypt.js
./src/pages/api/auth/[...nextauth].ts
./src/app/lib/getCurrentUser.ts
./src/app/providers/Provider.tsx- error ./node_modules/@mapbox/node-pre-gyp/lib/clean.js:8:0
Module not found: Can't resolve 'fs'
https://nextjs.org/docs/messages/module-not-found
Import trace for requested module:
./node_modules/@mapbox/node-pre-gyp/lib/ sync ^\.\/.*$
./node_modules/@mapbox/node-pre-gyp/lib/node-pre-gyp.js
./node_modules/bcrypt/bcrypt.js
./src/pages/api/auth/[...nextauth].ts
./src/app/lib/getCurrentUser.ts
./src/app/providers/Provider.tsx
- wait compiling /favicon.ico/route (client and server)...
- error ./node_modules/@mapbox/node-pre-gyp/lib/util/nw-pre-gyp/index.html
Module parse failed: Unexpected token (1:0)
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
> <!doctype html>
| <html>
| <head>
Import trace for requested module:
./node_modules/@mapbox/node-pre-gyp/lib/util/nw-pre-gyp/index.html
./node_modules/@mapbox/node-pre-gyp/lib/ sync ^\.\/.*$
./node_modules/@mapbox/node-pre-gyp/lib/node-pre-gyp.js
./node_modules/bcrypt/bcrypt.js
./src/pages/api/auth/[...nextauth].ts
./src/app/lib/getCurrentUser.ts
./src/app/providers/Provider.tsx3 Replies
New Zealand
looks to me like an issue with the @mapbox package, did it work before you installed it?
@New Zealand looks to me like an issue with the @mapbox package, did it work before you installed it?
Weevil parasitoidOP
hi sorry for the late response, I just saw your message... doing a little research I came across some other people that stumbled upon the same issue using next-auth + next.js 13.4.4
seems like people opted by downgrading their next version... thing is I don't know what other dependencies I should downgrade along with next