Skip to content

Support postcss-load-config 4 #519

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

Closed
kyrylkov opened this issue May 23, 2022 · 2 comments · Fixed by #520
Closed

Support postcss-load-config 4 #519

kyrylkov opened this issue May 23, 2022 · 2 comments · Fixed by #520

Comments

@kyrylkov
Copy link

No description provided.

@frederikhors
Copy link
Contributor

In a SvelteKit project:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/postcss-load-config
npm ERR!   dev postcss-load-config@"4.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peerOptional postcss-load-config@"^2.1.0 || ^3.0.0" from [email protected]
npm ERR! node_modules/svelte-preprocess
npm ERR!   dev svelte-preprocess@"4.10.6" from the root project
npm ERR!   svelte-preprocess@"^4.0.0" from [email protected]
npm ERR!   node_modules/svelte-check
npm ERR!     dev svelte-check@"2.7.1" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/postcss-load-config
npm ERR!   peerOptional postcss-load-config@"^2.1.0 || ^3.0.0" from [email protected]
npm ERR!   node_modules/svelte-preprocess
npm ERR!     dev svelte-preprocess@"4.10.6" from the root project
npm ERR!     svelte-preprocess@"^4.0.0" from [email protected]
npm ERR!     node_modules/svelte-check
npm ERR!       dev svelte-check@"2.7.1" from the root project

@alex-way
Copy link

Fix for those scratching their heads:

npm install postcss-load-config@^3.1.4

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.

3 participants