Repository navigation
bug: prompting when invoked programmatically #242
Description
Whenever a new option is added, existing programmatic integrations can break unless they explicitly set that option, since the user may be prompted for input (and there might not even be a user!)
In programmatic scenarios, create-package-json should never prompt the user. It should have defaults for everything, unless there is anything that is truly required, in which case it should throw an error if it's missing
Activity
[-]bug: create-package-json should never prompt when invoked programmatically[/-][+]bug: never prompt when invoked programmatically[/+][-]bug: never prompt when invoked programmatically[/-][+]bug: prompting when invoked programmatically[/+]wesleytodd commentedon Jan 8, 2026
The ideal here IMO is to decouple the methods that are exposed into three categories:
read&writefor composition into other workflows (what we should have been using)Since I have been touching this stuff again I have been considering what the next (unfortunately breaking) changes should look like, and I think I need to start with a new major in
optato address some of the underlying design choices for api composition that were made there. In general I think the idea is still solid (basic JS composition/POJO configuration with opinionated merging of cli/programitic/prompt input), but it needs to solve for 2 specific things:So, all this to say that I think the changes this package requires mean a new major and I think we need to do a major under the hood to best achieve that here. If we want we can skip it and do two majors (one to fix these apis, and one to update the foundation) but I doubt that will happen unless someone has more time to work on this than I have over the years.