Skip to content

optionalDependencies are not optional #844

@3LOK

Description

@3LOK

Do you want to request a feature or report a bug?
Feature

What is the current behavior?
I've read you don't really support optionalDependencies (for the deterministic feature). We use this heavily with our CI so our CI can use internal tools for publishing packages, while allowing public usage of the published package.

Is there any plan on solving this issue, or will optionalDependencies never be really optional in Yarn?

Note: --ignore-optional doesn't work as well, as you can see here:

yarn add redux-saga-tester --ignore-optional

If the current behavior is a bug, please provide the steps to reproduce.
Create a package.json file, add one of the following to it:

  "optionalDependencies":{
     "unknown-package-9999":"*"
  }

or

  "optionalDependencies":{
     "@wix/wnpm-ci":"*"
  }

What is the expected behavior?
As described here:

If a dependency can be used, but you would like npm to proceed if it cannot be found or fails to install, then you may put it in the optionalDependencies object

Gracefully continue installing other packages, and succeed if the others succeed.

Please mention your node.js, yarn and operating system version.
Node v6.2.0
Yarn v0.15.1
OSX 10.11.2

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions