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

prettier.resolveConfig.sync is not a function #168

Closed
kamalkech opened this issue Sep 13, 2023 · 6 comments
Closed

prettier.resolveConfig.sync is not a function #168

kamalkech opened this issue Sep 13, 2023 · 6 comments

Comments

@kamalkech
Copy link

any idea how to fixe this issue ??

TypeError: _prettier.resolveConfig.sync is not a function
    at /my-project/node_modules/.pnpm/[email protected][email protected]/node_mo
dules/pretty-quick/dist/isSupportedExtension.js:12:30
    at Array.filter (<anonymous>)
    at _default (/my-project/node_modules/.pnpm/[email protected][email protected]
.3/node_modules/pretty-quick/dist/index.js:53:157)
@blimmer
Copy link

blimmer commented Sep 14, 2023

See #164 - I've been moving to lint-staged

@kasir-barati
Copy link

Same here. My packages version:

"@types/jest": "^29.5.11",
"@typescript-eslint/eslint-plugin": "^6.15.0",
"@typescript-eslint/parser": "^6.15.0",
"eslint": "^8.56.0",
"eslint-config-prettier": "^9.1.0",
"eslint-plugin-jest": "^27.6.0",
"eslint-plugin-prettier": "^5.1.0",
"eslint-plugin-unused-imports": "^3.0.0",
"husky": "^8.0.3",
"jest": "^29.7.0",
"prettier": "^3.1.1",
"pretty-quick": "^3.1.3",
"ts-jest": "^29.1.1",
"typescript": "^5.3.3"

@NivEz
Copy link

NivEz commented Dec 28, 2023

@kasir-barati I use "prettier": "^2.8.0" altough it's older and it works for me.

@JounQin
Copy link
Member

JounQin commented Jan 15, 2024

Duplicate of #164

@JounQin JounQin marked this as a duplicate of #164 Jan 15, 2024
@JounQin JounQin closed this as not planned Won't fix, can't repro, duplicate, stale Jan 15, 2024
@kasir-barati
Copy link

kasir-barati commented Jan 15, 2024

@NivEz I really do not wanna, and like to downgrade it unless there is a strong reason -- something like old codebase, tight deadlines that won't leave room for other kind of stuff.

but under normal circumstances I would prefer to stick to the latest changes as much as possible

@JounQin
Copy link
Member

JounQin commented Jan 15, 2024

@kasir-barati

See #165 (comment)

I'll take over @azz's place and help to maintain this package in few days. 🍻

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

No branches or pull requests

5 participants