Closed (works as designed)
Project:
Drupal core
Version:
8.9.x-dev
Component:
Claro theme
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
26 Mar 2020 at 15:31 UTC
Updated:
27 Mar 2020 at 09:18 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
jungleComment #3
kostyashupenkoOn my side i can't reproduce this issue
Comment #4
jungle@kostyashupenko. thanks for reviewing!
It happens to me, see the gif (wrong gif, edited, reupload next)
not sure whether removing
core/node_modulesand reinstall node_modules helps reproducing on your local.Comment #5
jungleComment #6
jungleAha, found it
It only happens using npm to install packages.
It is an issue of my local env. using yarn, it's ok.
Comment #7
jungleFixed the gyp error by reinstall the command line tools.
Confirmed that using npm to install the packages -> reproduced. However, using yarn to install the packages, everything is ok.
As yarn is preferred with core development, "Drupal core using PostCSS for development" https://www.drupal.org/node/3084859
Closing this issue is ok for me.
Comment #8
longwaveyarn follows yarn.lock, which pins specific versions of packages (like composer.lock does). We don't have a lockfile for npm so you will get the latest versions of packages, at least one of which must be newer and causes the different behaviour.
Closing as suggested in #7.