You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Installing a module which has a postinstall script which utilises the Inquirer module causes yarn to exit with error code 1 without allowing the user to interact with the CLI
Command
yarn install [module which contains postinstall]
What is the current behavior?
Exits with code 1, giving the output as whatever the first prompt is.
This does not seem to happen when running yarn run postinstall in the module directly
What is the expected behavior?
Interactive CLI should run as normal - just as it does when installing with npm
Steps to Reproduce
Find a module which utilises an interactive CLI in postinstall. For this example I'm using bsian03/AxonCore#dev-docs (my fork of a repository which I'm working on dynamic typings based on user input for)
Install that module
Environment
Node Version: 12.9.1
Yarn v1 Version: 1.22.4
OS and version: Windows 10 Home, Build 18362 (10.0.18362)
The text was updated successfully, but these errors were encountered:
Just a note, our CI errors with code 130 and not code 1 as I mentioned, code 1 only seems to happen upon user installation
This is no longer relevant and the error code with the CI has been fixed
Bug description
Installing a module which has a postinstall script which utilises the Inquirer module causes yarn to exit with error code 1 without allowing the user to interact with the CLI
Command
What is the current behavior?
Exits with code 1, giving the output as whatever the first prompt is.
This does not seem to happen when running
yarn run postinstall
in the module directlyWhat is the expected behavior?
Interactive CLI should run as normal - just as it does when installing with npm
Steps to Reproduce
bsian03/AxonCore#dev-docs
(my fork of a repository which I'm working on dynamic typings based on user input for)Environment
12.9.1
1.22.4
The text was updated successfully, but these errors were encountered: