Change dev and build commands to use npm scripts to allow remix cli

[mattmazzola]

Issue

The existing docs suggest using commands remix dev or remix build; the direct use of remix will fail (I believe unless this package is installed globally)

D:\repos\universe-timeline-remix [master]> remix vite:dev
remix: The term 'remix' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Solution

Invoke the same commands through NPM scripts, which makes all the binary packages from the current project available

package.json of new SPA project

...
  "scripts": {
    "build": "remix vite:build",
    "dev": "remix vite:dev",
    "lint": "eslint --ignore-path .gitignore --cache --cache-location ./node_modules/.cache/eslint .",
    "preview": "vite preview",
    "typecheck": "tsc"
  }
...

npm run dev

npm run build

Closes: N/A

• Docs
• Tests

Testing Strategy:

Run commands on new SPA project verify successful execution

[changeset-bot]

⚠️ No Changeset found

Latest commit: 794587a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[kiliman]

I think it might be better to preface the commands with npx instead of relying on npm scripts. This way the user knows the exact command they need to run.

npx remix vite:build
npx remix vite:dev

[brophdawg11]

I agree prefixing with npx is more explicit - thanks for the PR!