-
-
Notifications
You must be signed in to change notification settings - Fork 188
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
Dedupe dependencies. #327
Comments
I guess one thing to do is to contribute to each dependencies. |
I compiled a list of packages to be updated to dedupe the dependencies.
I will see if they accept PR's for these. |
I am the author of most packages so there won't be any problem for most ;)
|
I merged the PR you made including this one MoOx/reduce-function-call#5. chalk updates for supports-color has landed a while ago. it seems to be in 1.1.2. |
I don't know how I missed that |
The latest version of |
@wtgtybhertgeghgtwtg any update on the work done here? |
More duplicates have sprung up. I will compile a list shortly. |
Ouch. Anything to share on how to catch these? |
There's a visualization tool: http://npm.anvaka.com/#/view/2d/postcss-cssnext |
#401 might help... My bad on this... |
|
Several of the packages on which
postcss-cssnext
depends share dependencies (postcss
,balanced-match
, et cetera). However, since some of them are pinned to difference versions than others, multiple versions of these sub dependencies are downloaded. For[email protected]
, it looks like four versions ofcolor
, three versions ofbalanced-match
, and two versions of eachsupports-color
,postcss-selector-parser
,color-string
,color-name
, andcolor-convert
are required. I am not sure if it is an actionable issue, but could something be done so that these can be deduped?The text was updated successfully, but these errors were encountered: