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

using yarn as replacement does not work #82

Closed
morloderex opened this Issue Jan 11, 2017 · 4 comments

Comments

Projects
None yet
5 participants
@morloderex

morloderex commented Jan 11, 2017

Hello, today i decided to try out this package.
I went ahead and installed the package but NOT through npm instead i tried to install it with yarn.

But when i run any of the npm scripts described in the documentation compilation fails with a message saying something like cross-env is not found.

I know this is specific to a yarn installation because with a traditional npm install it works without any issue.

Anyone who can say anything about way this is the case?

@JeffreyWay

This comment has been minimized.

Show comment
Hide comment
@JeffreyWay

JeffreyWay Jan 11, 2017

Owner

There's a GitHub issue for the Yarn repo to get that fixed. So closing for now.

Owner

JeffreyWay commented Jan 11, 2017

There's a GitHub issue for the Yarn repo to get that fixed. So closing for now.

@Evertt

This comment has been minimized.

Show comment
Hide comment
@Evertt

Evertt Jan 14, 2017

@JeffreyWay, can you maybe point me to the issue you're talking about? I can't find it on the yarn repo.

Evertt commented Jan 14, 2017

@JeffreyWay, can you maybe point me to the issue you're talking about? I can't find it on the yarn repo.

@mathieutu

This comment has been minimized.

Show comment
Hide comment
@mathieutu

mathieutu Jan 19, 2017

@Evertt I've posted a comment on theses two issues for yarn which seem to be our problem:

They are supposed to be closed, but obviously not, looking at our case.

mathieutu commented Jan 19, 2017

@Evertt I've posted a comment on theses two issues for yarn which seem to be our problem:

They are supposed to be closed, but obviously not, looking at our case.

@adriaanzon

This comment has been minimized.

Show comment
Hide comment
@adriaanzon

adriaanzon Jan 19, 2017

Contributor

I think the problem is that the binaries of recursive dependencies don't end up in node_modules/.bin, like this issue: yarnpkg/yarn#2493

Only when you explicitly add them to your project (yarn add --dev cross-env webpack) the binaries will end up in there.

Contributor

adriaanzon commented Jan 19, 2017

I think the problem is that the binaries of recursive dependencies don't end up in node_modules/.bin, like this issue: yarnpkg/yarn#2493

Only when you explicitly add them to your project (yarn add --dev cross-env webpack) the binaries will end up in there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment