Skip to content
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

yarn workspace should create symlink even if sub-project directory does not exists #5940

Open
victornoel opened this issue Jun 6, 2018 · 2 comments
Assignees
Labels

Comments

@victornoel
Copy link
Contributor

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

Feature

What is the current behavior?

If the workspaces property refers to a non-existing directory, yarn does not create the symlink.

If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?

If the workspaces property refers to a non-existing directory, yarn should create the symlink anyway.
The reason being that sometimes, depending on how the build is done, the sub-project is actually a built artifacts that is created AFTER yarn is executed.

Please mention your node.js, yarn and operating system version.

Yarn 1.7.0

@ghost ghost assigned torifat Jun 6, 2018
@ghost ghost added the triaged label Jun 6, 2018
@victornoel
Copy link
Contributor Author

Hm wait, that does not make sense, if there is no package.json I guess we can't know the name.

Sorry :)

@victornoel
Copy link
Contributor Author

Well I reopen in case I'm wrong :)

@victornoel victornoel reopened this Jun 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants