Error running app
See original GitHub issueHello, I followed the README carefully, but when I tried running the app I got this error below:
npm run dev 1 ↵ blkboxng@Chris
> nextjs-commerce@1.0.0 dev
> next dev
ready - started server on 0.0.0.0:3000, url: http://localhost:3000
info - Loaded env from /Users/blkboxng/Desktop/publicTrs/snaphubs/.env.development
info - Using webpack 4. Reason: future.webpack5 option not enabled https://nextjs.org/docs/messages/webpack5
Browserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db
Why you should do it regularly:
https://github.com/browserslist/browserslist#browsers-data-updating
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './lib/parser' is not defined by "exports" in /Users/blkboxng/Desktop/publicTradesProperties/snaphubs/node_modules/postcss/package.json
at new NodeError (node:internal/errors:388:5)
at throwExportsNotFound (node:internal/modules/esm/resolve:440:9)
at packageExportsResolve (node:internal/modules/esm/resolve:719:3)
at resolveExports (node:internal/modules/cjs/loader:488:36)
at Module._findPath (node:internal/modules/cjs/loader:528:31)
at Module._resolveFilename (node:internal/modules/cjs/loader:932:27)
at mod._resolveFilename (/Users/blkboxng/Desktop/publicTradesProperties/snaphubs/node_modules/next/dist/build/webpack/require-hook.js:4:1784)
at Module._load (node:internal/modules/cjs/loader:787:27)
at Module.require (node:internal/modules/cjs/loader:1012:19)
at require (node:internal/modules/cjs/helpers:102:18)
at 552 (/Users/blkboxng/Desktop/publicTradesProperties/snaphubs/node_modules/next/dist/compiled/postcss-scss/scss-syntax.js:1:11590)
at __nccwpck_require__ (/Users/blkboxng/Desktop/publicTradesProperties/snaphubs/node_modules/next/dist/compiled/postcss-scss/scss-syntax.js:1:11735)
at 270 (/Users/blkboxng/Desktop/publicTradesProperties/snaphubs/node_modules/next/dist/compiled/postcss-scss/scss-syntax.js:1:400)
at __nccwpck_require__ (/Users/blkboxng/Desktop/publicTradesProperties/snaphubs/node_modules/next/dist/compiled/postcss-scss/scss-syntax.js:1:11735)
at 327 (/Users/blkboxng/Desktop/publicTradesProperties/snaphubs/node_modules/next/dist/compiled/postcss-scss/scss-syntax.js:1:260)
at __nccwpck_require__ (/Users/blkboxng/Desktop/publicTradesProperties/snaphubs/node_modules/next/dist/compiled/postcss-scss/scss-syntax.js:1:11735) {
code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}
The error says to run npx browserslist@latest --update-db
, and after running that I got another error:
npx browserslist@latest --update-db 1 ↵ blkboxng@Chris
New version: 1.0.30001366
Removing old caniuse-lite from lock file
Installing new caniuse-lite version
$ npm install caniuse-lite
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @reach/portal@0.11.2
npm ERR! Found: react@17.0.2
npm ERR! node_modules/react
npm ERR! react@">=14" from @builder.io/react@1.1.47
npm ERR! node_modules/@builder.io/react
npm ERR! peer @builder.io/react@"^1.1.0" from @builder.io/widgets@1.2.19
npm ERR! node_modules/@builder.io/widgets
npm ERR! @builder.io/widgets@"^1.2.19" from the root project
npm ERR! @builder.io/react@"^1.1.47" from the root project
npm ERR! react@">=14" from @builder.io/widgets@1.2.19
npm ERR! node_modules/@builder.io/widgets
npm ERR! @builder.io/widgets@"^1.2.19" from the root project
npm ERR! 48 more (@next/react-dev-overlay, next, @emotion/core, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.8.0" from @reach/portal@0.11.2
npm ERR! node_modules/@reach/portal
npm ERR! @reach/portal@"^0.11.2" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: react@16.14.0
npm ERR! node_modules/react
npm ERR! peer react@"^16.8.0" from @reach/portal@0.11.2
npm ERR! node_modules/@reach/portal
npm ERR! @reach/portal@"^0.11.2" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /Users/blkboxng/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/blkboxng/.npm/_logs/2022-07-13T17_21_52_408Z-debug-0.log
Error: Command failed: npm install caniuse-lite
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @reach/portal@0.11.2
npm ERR! Found: react@17.0.2
npm ERR! node_modules/react
npm ERR! react@">=14" from @builder.io/react@1.1.47
npm ERR! node_modules/@builder.io/react
npm ERR! peer @builder.io/react@"^1.1.0" from @builder.io/widgets@1.2.19
npm ERR! node_modules/@builder.io/widgets
npm ERR! @builder.io/widgets@"^1.2.19" from the root project
npm ERR! @builder.io/react@"^1.1.47" from the root project
npm ERR! react@">=14" from @builder.io/widgets@1.2.19
npm ERR! node_modules/@builder.io/widgets
npm ERR! @builder.io/widgets@"^1.2.19" from the root project
npm ERR! 48 more (@next/react-dev-overlay, next, @emotion/core, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.8.0" from @reach/portal@0.11.2
npm ERR! node_modules/@reach/portal
npm ERR! @reach/portal@"^0.11.2" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: react@16.14.0
npm ERR! node_modules/react
npm ERR! peer react@"^16.8.0" from @reach/portal@0.11.2
npm ERR! node_modules/@reach/portal
npm ERR! @reach/portal@"^0.11.2" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /Users/blkboxng/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/blkboxng/.npm/_logs/2022-07-13T17_21_52_408Z-debug-0.log
at checkExecSyncError (node:child_process:820:11)
at Object.execSync (node:child_process:891:15)
at updateDB (/Users/blkboxng/Desktop/publicTradesProperties/snaphubs/node_modules/browserslist/update-db.js:146:18)
at Object.<anonymous> (/Users/blkboxng/Desktop/publicTradesProperties/snaphubs/node_modules/browserslist/cli.js:40:3)
at Module._compile (node:internal/modules/cjs/loader:1112:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1166:10)
at Module.load (node:internal/modules/cjs/loader:988:32)
at Module._load (node:internal/modules/cjs/loader:834:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
Problem with `npm install` call. Run it manually.
Can someone help resolve this?
Thanks in advance
Issue Analytics
- State:
- Created a year ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Error running 'app': No target device found. - Code2care
The above error you may get when trying to run your Android Application on IntelliJ Android Studio, it means that there is no...
Read more >Instant Run requires 'Tools | Android | Enable ADB integration ...
If the "Error running app: Instant Run requires 'Tools | Android | Enable ADB integration' to be enabled." issue occurs while using the ......
Read more >Xcode error by running app on real… | Apple Developer Forums
My app is running perfectly in the simulator (Xcode Beta and iOS 9), but when I try to run it on my real...
Read more >Activity not started, unable to resolve Intent { act=android ...
Description trying to run genymotion simulator .. followed the instructions but getting the following error Error running adb: Error running app.
Read more >Known issues with Android Studio and Android Gradle Plugin
Apps using the Database Inspector may crash when running on the Android 11 emulator, with an error like the following appearing in logcat:....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks, downgrading node version resolved the issue … Thanks!!
@ChrisB007 I got the same error using node v18.4. For now try using node v12-v15 and lmk if you’re still running into the issue. Thanks!