Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error! Can't parse json file #39737

Closed
1 task done
koshimazaki opened this issue Aug 18, 2022 · 3 comments
Closed
1 task done

Error! Can't parse json file #39737

koshimazaki opened this issue Aug 18, 2022 · 3 comments
Labels
bug Issue was opened via the bug report template. please add a complete reproduction The issue lacks information for further investigation

Comments

@koshimazaki
Copy link

Verify canary release

  • I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
Platform: darwin
Arch: arm64
Version: Darwin Kernel Version 21.6.0: Sat Jun 18 17:07:22 PDT 2022; root:xnu-8020.140.41~1/RELEASE_ARM64_T6000
Binaries:
Node: 16.13.2
npm: 8.15.1
Yarn: 3.2.1
pnpm: N/A
Relevant packages:
next: 12.2.4
eslint-config-next: N/A
react: 17.0.2
react-dom: 17.0.2

What browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

Vercel

Describe the Bug

I keep getting error once trying to build project with Vercel. It builds fine locally. Is there something i am overlooking? Only json file I have in repo is package.json

Running "vercel build"

15:22:31.883 | Vercel CLI 28.0.1
15:22:31.976 | Error! Can't parse json file

Expected Behavior

Congratulations built with success! ;)

Link to reproduction

see json file contents below

To Reproduce

{
"private": true,
"scripts": {
"dev": "next dev",
"build": "next build",
"start": "next start"
},
"dependencies": {
"axios": "^0.27.2",
"express": "^4.18.1",
"googleapis": "^105.0.0",
"next": "latest",
"react": "^17.0.2",
"react-dom": "^17.0.2",
"react-player": "^2.10.1",
"redux": "^4.2.0",
"semantic-ui-css": "^2.4.1",
"semantic-ui-react": "^2.1.3"
}
}

@koshimazaki koshimazaki added the bug Issue was opened via the bug report template. label Aug 18, 2022
@balazsorban44 balazsorban44 added the please add a complete reproduction The issue lacks information for further investigation label Aug 19, 2022
@koshimazaki
Copy link
Author

Case sensitive imports / file names was an issue at then end. Exactly as in here:
#18176

Installing ESlint helped and so did not entering the env variables.

@koshimazaki
Copy link
Author

Just leaving it here in case someone is experiencing the same error. This is related to env variables. It doesn't work for me by inputing Google private key in the Vercel interface. Looks like im not alone.

vercel/vercel#749

@wariomx
Copy link

wariomx commented Sep 19, 2022

Did you solve it? i hava the same issue, in vercel
Error: Can't parse json file

@vercel vercel locked and limited conversation to collaborators Sep 20, 2022
@ijjk ijjk converted this issue into discussion #40730 Sep 20, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
bug Issue was opened via the bug report template. please add a complete reproduction The issue lacks information for further investigation
Projects
None yet
Development

No branches or pull requests

3 participants