bower: bower init failing to bring the interactive prompt to create bower.json
After updating bower to 1.2.1, the bower init command seems to fail. When running the bower init the follow result is shown:
- bower ENOINT Register requires interactive
Here is the Stack Trace when run in verbose mode:
bower ENOINT Register requires interactive
Stack trace:
Error: Register requires interactive
at createError (/usr/local/lib/node_modules/bower/lib/util/createError.js:4:15)
at /usr/local/lib/node_modules/bower/lib/commands/init.js:24:34
at process.startup.processNextTick.process._tickCallback (node.js:244:9)
Console trace:
Trace
at StandardRenderer.error (/usr/local/lib/node_modules/bower/lib/renderers/StandardRenderer.js:74:17)
at Logger.<anonymous> (/usr/local/lib/node_modules/bower/bin/bower:108:18)
at Logger.EventEmitter.emit (events.js:96:17)
at Logger.emit (/usr/local/lib/node_modules/bower/node_modules/bower-logger/lib/Logger.js:29:39)
at /usr/local/lib/node_modules/bower/lib/commands/init.js:24:20
at process.startup.processNextTick.process._tickCallback (node.js:244:9)
System info:
Bower version: 1.2.1
Node version: 0.8.19
OS: Darwin 13.0.0 x64
About this issue
- Original URL
- State: closed
- Created 11 years ago
- Comments: 38 (8 by maintainers)
@IshanDemon running ‘bower init’ works on windows cmd (but did not work with git bash command line for a mysterious reason). thanks!
If you are using windows run bower init using CMD
OR
if you are using git bash follow these steps:
do this from the run command cmd.exe /C “C:\Program Files\Git\bin\bash.exe” --login -i then bower init will work and you can do everything in minw64, mintty, or git-bash whatever it is called.
This is still an issue w/
bower 1.8.0ongit version 2.10.1.windows.1Using
cmdovergit bashis not a fix,… it’s a step backwards.Will try some of the following solutions mentioned above and report back.
Does not work with cygwin. Tried
bower initfirstly, thenbower init --config.interactive.+1 same here when using cygwin shell. In cmd all works fine.
i met it today。the way i slove it is using windows cmd instead of git bash.It worked! enjoy it. buddy
I’ve tried to downgrade the version to bower 0.10.0 but it doesn’t work well. The bower init configuration works fine for few seconds then it hangs up your terminal. The solution is found in on its documentation. It’s not supporting MinTTY which causes this problem. Here is the solution:
Hey @jinmatt!
npm install bower -g) or are you actually have it cloned locally andnpm link?In case you have a linked copy of bower in
2.you have to donpm installinside the cloned bower directory.The interactive flag is being set here: https://github.com/bower/bower/blob/master/lib/config.js#L11 you can debug that with a
console.log(config)before the if statement and one afterwards, includingprocess.titleandisatty.Note that you can enable it anyway with
--config.interactive, but worth investigating why your terminal is not a reporting itself as a tty.I’m having this problem with bower in cygwin. This used to work some time ago, but for some reason it stopped after upgrading to the latest version.
I have the same problem 😢 with Git Bash, but it works well with cmd