Skip to content
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

yarn start error,tsconfig.json格式确认是对的 #102

Open
freemanxzx opened this issue May 14, 2024 · 6 comments
Open

yarn start error,tsconfig.json格式确认是对的 #102

freemanxzx opened this issue May 14, 2024 · 6 comments

Comments

@freemanxzx
Copy link

image

clone的main里的代码

前序操作唯一的异常是yarn的时候有几个插件安装失败

image

@erha19
Copy link
Member

erha19 commented May 14, 2024

@freemanxzx 你使用的 node 版本是多少?试试用 node16 去安装及执行

@freemanxzx
Copy link
Author

freemanxzx commented May 14, 2024

用的node 16 @erha19

@erha19
Copy link
Member

erha19 commented May 14, 2024

@freemanxzx 贴一下你本地的 tsconfig.json 文件,这里的报错信息指向的是你本地这个文件不符合 json 格式要求,你可以尝试修改下部分内容看能不能解决这个问题,MacOS 还复现不了这个问题

@freemanxzx
Copy link
Author

{
"compilerOptions": {
"module": "commonjs",
"target": "es2017",
"baseUrl": "src",
"moduleResolution": "node",
"strict": true,
"strictPropertyInitialization": false,
"sourceMap": true,
"experimentalDecorators": true,
"emitDecoratorMetadata": true,
"importHelpers": true,
"resolveJsonModule": true,
"noFallthroughCasesInSwitch": true,
"forceConsistentCasingInFileNames": true,
"downlevelIteration": true,
"noEmitOnError": false,
"noImplicitAny": false,
"skipLibCheck": true,
"strictFunctionTypes": false,
"jsx": "react",
"lib": [
"dom",
"esnext",
"webworker"
],
"typeRoots": [
"./node_modules/@types"
]
},
"exclude": [
"./extensions//*",
"./workspace/
/",
"./hosted/**/
",
"./dist-node//*",
"./dist/
/",
"./node_modules/**/
"
]
}

@erha19

@freemanxzx
Copy link
Author

image
image

@erha19
Copy link
Member

erha19 commented May 14, 2024

@freemanxzx 你试一下这个分支代码 #103

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants