-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[Error]: Breaking change introduced in ver. 9.3.6 (TypeError: split called on null or undefined) #1561
Comments
That'd help me understand if it's an issue fixing within Inquirer, or if it's a bug plop needs to fix. |
Okay so I was digging into node-plop and it's working and found out that it's only happening when I was using bypassPrompts functionality of runPrompts I believe the issue is at node-plop's end. I would like your remark as to whether this is enough to consider this issue resolved and close this issue . |
Well I'd like to know someone fixes this on plop side. Seems like it confuses many of their users. I can push a hotfix to the 9.x release branch. |
|
@SBoudrias,
Breaking change introduced in this commit ec78662#diff-b24d4a707495e5e2f210d200fab3550db18877ded7d01e729bb73e0c9b103c55
I am using
node-plop
in my project and after this commit I believe I am getting an error on running only the prompts.I think this is a breaking change
Please look at this issue for more context: plopjs/plop#445
The text was updated successfully, but these errors were encountered: