emulsify-ds / emulsify-drupal

Drupal theme built with Storybook and Webpack

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Conflicting dependencies, could not resolve

jennypns opened this issue · comments

emulsify version (see releases):
4.2.0

node version:
16.16.0

npm (or yarn) version:
8.11.0

What you did:
Trying to install emulsify drupal theme from scratch into a clean directory, following these steps: https://modulesunraveled.wistia.com/medias/7cdtb3k40h (yes even after removing the prepare: husky install line)

What happened:
When running npm install I get three warnings about unmet or conflicting dependencies.

Problem description:

$/www/mysite/web/themes/custom/my_theme$ npm install
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: postcss-prefix-selector@1.14.0
npm WARN Found: postcss@5.2.18
npm WARN node_modules/svg-baker/node_modules/postcss
npm WARN   postcss@"^5.2.17" from svg-baker@1.7.0
npm WARN   node_modules/svg-baker
npm WARN     svg-baker@"^1.7.0" from svg-baker-runtime@1.4.7
npm WARN     node_modules/svg-baker-runtime
npm WARN     1 more (svg-sprite-loader)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer postcss@"7.x || 8.x" from postcss-prefix-selector@1.14.0
npm WARN node_modules/svg-baker/node_modules/postcss-prefix-selector
npm WARN   postcss-prefix-selector@"^1.6.0" from svg-baker@1.7.0
npm WARN   node_modules/svg-baker
npm WARN
npm WARN Conflicting peer dependency: postcss@8.4.14
npm WARN node_modules/postcss
npm WARN   peer postcss@"7.x || 8.x" from postcss-prefix-selector@1.14.0
npm WARN   node_modules/svg-baker/node_modules/postcss-prefix-selector
npm WARN     postcss-prefix-selector@"^1.6.0" from svg-baker@1.7.0
npm WARN     node_modules/svg-baker

Suggested solution:
I know they're just warnings, but it feels like these dependencies should be resolved.

┆Issue is synchronized with this Clickup by Unito

@jennypns I played around a bit today to see if there was a quick update that would fix this, and I didn't find anything. Since this is just a warning, I expect this may wait until we do a big dependency update.