peerDependencies

[monolithed]

I propose to use postcss as peerDependency.
It seems more consistent with npm 3.

[jonathantneal]

@monolithed, you can require('precss') and use PreCSS without require('postcss'), since PostCSS plugins are given a mirrored process method.

In other words, precss.process(YOUR_CSS, YOUR_OPTIONS) mirrors PostCSS’ process method.

Does this answer your concern, or do I not understand something about peerDependency?

[monolithed]

@jonathantneal, I mean flat directory structure.
For example:

➜ npm2 install grunt-postcss precss
➜ tree -d node_modules
....
├── precss
│   ├── node_modules/postcss
│   ├── node_modules/postcss-custom-properties
...
├── grunt-postcss
│   ├── node_modules/postcss
...

➜ npm3 install grunt-postcss precss
➜ tree -d node_modules
....

grunt-postcss
postcss
precss
postcss-custom-media
postcss-custom-properties
rgb
source-map
....

In other words peerDependencies allow to exclude duplication of packages.

PS: Actually, I've another issue for grunt-postcss

[jonathantneal]

I believe peerDependencies are now deprecated.

[monolithed]

The previous behavior of peerDependencies is now obsolete.
For more details npm/npm#6565 (comment)

[jonathantneal]

Closing this due to inactivity.