Description
As user using remix-kit, it would be nice to know what each of the remix-kit commands does
Example Scenario
- I create a new remix app (Remix App server)
- Setup
remix-kit
> cd ./your-remix-app
> npx remix-kit@latest install
> npm run vite:dev
- I check the my
package.json & see that there are new commands added to my scripts section:

when should I use some of the commands over the other?
"vite:preview": "remix-kit preview", is straight forward IMO
but these other 3 are less straight forward:
"vite:dev": "remix-kit dev --origin http://localhost:3000",
"vite:preview": "remix-kit preview",
"dev:server": "remix-kit preview"
Questions
- Are
"vite:preview" and ``"dev:server"` use the same shell command, is this intentional? I found it confusing seeing 2 different script commands that each call the same thing
- When would i use
npm run vite:dev over npm run dev:server?
Suggested solution
Perhaps Adding documentation on each of the remix-kit commands, perhaps a table of when to use them
or
a new Remix CLI command that outputs what all the commands do in one STDOUT output
# we could link this in the README too
`npx remix-kit --help`
I think this is still useful:
npx remix [command] --help
Alternative
No response
Additional context
No response
Validations
Description
As user using
remix-kit, it would be nice to know what each of theremix-kitcommands doesExample Scenario
remix-kitpackage.json& see that there are new commands added to myscriptssection:when should I use some of the commands over the other?
"vite:preview": "remix-kit preview",is straight forward IMObut these other 3 are less straight forward:
"vite:dev": "remix-kit dev --origin http://localhost:3000","vite:preview": "remix-kit preview","dev:server": "remix-kit preview"Questions
"vite:preview"and ``"dev:server"` use the same shell command, is this intentional? I found it confusing seeing 2 different script commands that each call the same thingnpm run vite:devovernpm run dev:server?Suggested solution
Perhaps Adding documentation on each of the remix-kit commands, perhaps a table of when to use them
or
a new Remix CLI command that outputs what all the commands do in one STDOUT output
I think this is still useful:
Alternative
No response
Additional context
No response
Validations