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
Can't start new project #2179
Labels
Comments
watilde
added a commit
to watilde/yarn
that referenced
this issue
Dec 10, 2016
Normalize the author and repository field in package.json Fix for yarnpkg#2179. The interactive prompt of `yarn init` can't display the nested sub-question for the questions when there are no default values of the author/repository and the fields have Object values in `package.json`.
watilde
added a commit
to watilde/yarn
that referenced
this issue
Dec 10, 2016
Fix for yarnpkg#2179. The interactive prompt of `yarn init` can't display the nested sub-question for the questions when there are no default values of the author/repository and the fields have Object values in `package.json`.
bestander
pushed a commit
that referenced
this issue
Dec 13, 2016
Fix for #2179. The interactive prompt of `yarn init` can't display the nested sub-question for the questions when there are no default values of the author/repository and the fields have Object values in `package.json`.
Isn't it the same as #1924 ? |
@sebn Yes, thanks 👍 |
@bestander close; dupe of #1924 |
Sorry, my bad. I wrote the comment but missed to close it 😞 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Do you want to request a feature or report a bug?
A bug.
What is the current behavior?
When I try to init using the command
yarn init
, the following error occurs after the questionentry point (index.js)
:error An unexpected error occurred: "Cannot convert object to primitive value".
Please mention your node.js, yarn and operating system version.
node.js: v6.9.2
yarn: v0.17.10
Distributor ID: Ubuntu
Description: Ubuntu 16.04.1 LTS
Release: 16.04
Codename: xenial
Trace from the yarn-error.log file:
The text was updated successfully, but these errors were encountered: