generator-jhipster: jhipster command blocks on application/project name prompt
Overview of the issue
Not able to create a new JHipster application using just the prompts
Motivation for or Use Case
Should be able to create JHipster application using just the prompts
Reproduce the error
npm install -g generator-jhipstermkdir temp && cd tempjhipster- Select an app type. For me it does not matter
- App is now blocked at the app name question.
Related issues
https://github.com/jhipster/jhipster-kotlin/issues/149
JHipster Version(s)
6.0.1 6.1.0
JHipster configuration
INFO! Using JHipster version installed globally INFO! Executing jhipster:info INFO! Options: from-cli: true Welcome to the JHipster Information Sub-Generator
JHipster Version(s)
/home/pav/Development/temp/jhipster-java/temp
└── (empty)
cat: no such file or directory: .yo-rc.json
JHipster configuration, a .yo-rc.json file generated in the root folder
.yo-rc.json file
JDL for the Entity configuration(s) entityName.json files generated in the .jhipster directory
JDL entity definitions
Environment and Tools
java version “1.8.0_201” Java™ SE Runtime Environment (build 1.8.0_201-b09) Java HotSpot™ 64-Bit Server VM (build 25.201-b09, mixed mode)
git version 2.17.1
node: v10.15.2
npm: 6.9.0
yeoman: 2.0.5
yarn: 1.16.0
Docker version 18.09.6, build 481bc77
docker-compose version 1.23.2, build 1110ad01
Operating System
Ubuntu 18.04.2 LTS
- Checking this box is mandatory (this is just to show you read everything)
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 15 (15 by maintainers)
Commits related to this issue
- set inquirer npm dependency resolution to 6.3.1 fix #9952 — committed to PierreBesson/generator-jhipster by PierreBesson 5 years ago
- Merge pull request #9954 from PierreBesson/fix-inquirer-resolution Set inquirer npm dependency resolution to 6.3.1 fix #9952 — committed to jhipster/generator-jhipster by jdubois 5 years ago
- set inquirer npm dependency resolution to 6.3.1 fix #9952 — committed to Tcharl/generator-jhipster by PierreBesson 5 years ago
My process was to look at the diff between a newly generated package-lock.json and the one from the 6.1.0 release. Then I searched among the transitively updated packages which one had a recent npm release (manually). Then I expected that people must have already opened an issue on the GitHub project.
Awesome work @PierreBesson ! The good news is that @SBoudrias is a friend and an excellent coder, so this time to bug should be solved easily!!
I have found the problematic dependency: https://github.com/SBoudrias/Inquirer.js/issues/811