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

Init doesn't create a packages folder #591

Closed
xtuc opened this issue Feb 9, 2017 · 4 comments
Closed

Init doesn't create a packages folder #591

xtuc opened this issue Feb 9, 2017 · 4 comments
Labels

Comments

@xtuc
Copy link

xtuc commented Feb 9, 2017

In the README, the getting started section says that the lerna init command:

[...] will create a lerna.json configuration file as well as a packages folder.

Looking at the source code I think this behavior doesn't exists anymore, see InitCommand

Tested on lerna@2.0.0-beta.37

@gigabo
Copy link
Contributor

gigabo commented Feb 9, 2017

Nice catch @xtuc. That was removed from the documentation when #365 stopped creating the folder, but looks it was added back into the documentation in #517. I guess the resolution there should have been to update the website rather than the README. Should be solved by building the website from the README, which I think is underway in lerna/website#14.

dnalborczyk added a commit to dnalborczyk/lerna that referenced this issue Mar 21, 2017
_lerna_ init does not create a packages folder.

lerna#591
@jwb
Copy link
Contributor

jwb commented May 19, 2017

I wonder: if the website generation isn't making progress, should we prune out the details and just link to the README, so we aren't providing bad info to users?

@stale
Copy link

stale bot commented Dec 27, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Dec 27, 2018
@stale stale bot closed this as completed Jan 3, 2019
@lock
Copy link

lock bot commented Apr 3, 2019

This thread has been automatically locked because there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Apr 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants