-
-
Notifications
You must be signed in to change notification settings - Fork 431
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
Making node-sass a fully-fledged dependency #166
Conversation
In npm3, peerDeps aren't auto-installed anymore.
Sorry, specifying Since In other words: Your API surface to node-sass is much bigger than ours. Otherwise we would have tons of issues and PRs like "Update node-sass to x.y.z plz" |
I'm using npm3 now and it doesn't install node-sass automatically. |
Also I think this is the same with any other wrappers. You could keep the same semver as |
I know and that's good. node-sass should be the dependency of your project.
It's true, people are handling this differently. And while there are projects where your suggested approach is very reasonable (like for the phantomjs-package for example), I don't think that it fits here. The sass-loader is a link between webpack and node-sass. Following node-sass versions would ignore the fact that we also have to stay up-to-date with webpack: So, which version number should we follow then? Imho, the most robust solution to this problem is to have an own version number and to specify both as But you're right. I forgot to add |
I would love to hear alternatives from @iarna or @othiym23, but I guess there no new insights than already discussed at npm/npm#5080 npm/npm#6565 npm/npm#7495... |
hm..alright.. |
In npm3, peerDeps aren't auto-installed anymore.