1. 2
    Create a New Remix Project Using the remix-create CLI
    36s

Create a New Remix Project Using the remix-create CLI

Kent C. Dodds
InstructorKent C. Dodds

Share this video with your friends

Send Tweet
Published 3 months ago
Updated 3 months ago

New Remix projects can easily be created using the create-remix CLI. In this lesson, you’ll run the following script in your terminal window npx create-remix --template remix-run/indie-stack onewheel-blog.

Once that is ran it’ll create the project and automatically run the dev server on port 3000.

Kent C. Dodds: [0:00] We'll start by running npx create-remix with the --template flag of remix-run/indie-stack and we'll create it in our onewheel-blog. We will say, "Yes. I want to install."

[0:17] We will keep the TypeScript. Now, we can cd into our onewheel-blog directory and run npm run dev, and that will get our dev server up and running on port 3000. If we go to localhost:3000, we are all set up.

Marcus Holmgren
Marcus Holmgren
~ 3 months ago

Don't forget to rename file ".env.example" to ".env" before you start the application for the first time. Otherwise you will get a runtime error: Environment variable not found: DATABASE_URL.

Kent C. Dodds
Kent C. Doddsinstructor
~ 3 months ago

You shouldn't have to do that unless you choose not to have it run the install for you. If you do that then it will tell you to run the install manually and then run npx remix init which will do that for you.

ed leach
ed leach
~ 3 months ago

Initial install: almost 40,000 files adding up to about 1/2 a Gig. Amazing. (Says the old guy.)

Arti
Arti
~ 2 months ago

I am unable to get this up & running. I even tried selecting JS instead of TS but this consistently fails with this error message:

==== Running seed command ts-node --require tsconfig-paths/register prisma/seed.ts ... node:internal/modules/cjs/loader:944 throw err; ^

Error: Cannot find module './seed.ts' Require stack:

  • /Users/arti/learn/onewheel-blog/prisma/imaginaryUncacheableRequireResolveScript at Function.Module._resolveFilename (node:internal/modules/cjs/loader:941:15) at Function.resolve (node:internal/modules/cjs/helpers:99:19) at requireResolveNonCached (/Users/arti/learn/onewheel-blog/node_modules/ts-node/dist/bin.js:496:16) at getProjectSearchDir (/Users/arti/learn/onewheel-blog/node_modules/ts-node/dist/bin.js:466:40) at phase3 (/Users/arti/learn/onewheel-blog/node_modules/ts-node/dist/bin.js:268:27) at bootstrap (/Users/arti/learn/onewheel-blog/node_modules/ts-node/dist/bin.js:44:30) at main (/Users/arti/learn/onewheel-blog/node_modules/ts-node/dist/bin.js:32:12) at Object.<anonymous> (/Users/arti/learn/onewheel-blog/node_modules/ts-node/dist/bin.js:526:5) at Module._compile (node:internal/modules/cjs/loader:1109:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1138:10) { code: 'MODULE_NOT_FOUND', requireStack: [ '/Users/arti/learn/onewheel-blog/prisma/imaginaryUncacheableRequireResolveScript' ] } ====
Arti
Arti
~ 2 months ago

Ok, this was fixed by deleting the onewheel-blog folder & running the command again with a different name for the repo. ¯_(ツ)_/¯