The front door, and nothing else — it resolves the CLI and runs it.
$ npm create [email protected] my-app
It resolves @frontierjs/cli and runs fli new
What a new app looks like is written once, in the CLI. A create package with a scaffolder of its own is a second answer that drifts from the first release onward.
The target directory is pinned, not searched for
fli walks UP to find a project root, which is right when you are inside an app and wrong when npm create runs you inside an existing repo — without the pin the scaffold lands in that repo’s root.
Nothing — there is no common equivalent to swap out.
Arguments are forwarded untouched
Every flag the scaffolder has works here on the day it is added, because this package does not know what they are.
The rest of the stack