Mark Stosberg

Thanks. It sounds like `res.noContent` is specific to two status codes and would not help when checking that an empty body is returned with another status code. For example, if...

I'm looking forward to the new release with promise support.

@ljharb Yarn chooses to setup `registry.yarnpkg.org` as the source for most package downloads, not `npmjs.org`. This proxy can choose to return it's own codes, however, I'm not sure this proxy...

@ljharb Thanks for the feedback. I'll do that and report back.

First, you are already putting significant trust into the packages you are about to install. They can execute scripts as part of the installation with the user running the installer...

The PR looks good to me, but given https://github.com/yarnpkg/yarn/issues/2666 it could be good clarify whether `--ignore-optional` is intended to work only for the top-level package or also for all dependencies...

It's also not clear what `yarn ls --depth 0` is showing. I would expect it to list the same dependencies seen in `package.json`, but it lists many more. I suspect...

This should be re-opened, it's still not clear what `yarn list --depth 0` is showing. See: https://github.com/yarnpkg/website/pull/251#pullrequestreview-75150705

@olingern It does seem like `yarn list --depth 0` is showing flattened dependencies. I guess if you want the un-flattened dependencies, you can just open up `package.json`. If the current...

This issue can be closed.