Not intended to sound snarky. My question comes from a place of interest and ignorance.
I don鈥檛 know enough about Yeoman but we had a few constraints:
npm start, npm test and npm run build, and we don't want to make an impression that we will scaffold any code for you.react-scripts (which is the actual code). So you don't need to update the CLI when starting new projects: you always use latest react-scripts by default. For this to work, we need CLI to call init.js inside react-scripts so that we can safely change it in future versions without breaking backwards compat with the CLI.I鈥檓 not sure if Yeoman satisfies them and we didn鈥檛 want to lock ourselves into something that would be hard to change. Does this help?
Yes, thank you for taking the time to answer this @gaearon. :)
Closing...
Most helpful comment
I don鈥檛 know enough about Yeoman but we had a few constraints:
npm start,npm testandnpm run build, and we don't want to make an impression that we will scaffold any code for you.react-scripts(which is the actual code). So you don't need to update the CLI when starting new projects: you always use latestreact-scriptsby default. For this to work, we need CLI to callinit.jsinsidereact-scriptsso that we can safely change it in future versions without breaking backwards compat with the CLI.I鈥檓 not sure if Yeoman satisfies them and we didn鈥檛 want to lock ourselves into something that would be hard to change. Does this help?