Skip to content

Commit fcd642d

Browse files
committed
Fix references to rake tasks in README
1 parent 6d69dd0 commit fcd642d

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,10 +14,10 @@ These are the steps to get the current repository running on your machine.
1414
* Download the GitHub respository.
1515
* Install dependencies with `bundle install`
1616
* Start the Ruby on Rails application with `bin/dev`
17-
* Build the React application with `bin/rails react:preview`
17+
* Build the React application with `bin/rails react_router:preview`
1818
* Access `http://localhost:3000`
1919

20-
If you want to use the React Router development server with HMR, instead of building the React application, run the development server with `bin/rails react:dev`.
20+
If you want to use the React Router development server with HMR, instead of building the React application, run the development server with `bin/rails react_router:dev`.
2121
Then access the page with ``http://localhost:5173/react`.
2222
Note that you will not be able to switch between ERB and React pages with the React Router development server.
2323

@@ -52,7 +52,7 @@ In short, embracing loader-based fetching will improve the UI/UX of your applica
5252

5353
### Automatic Code-splitting
5454

55-
When you build the React Router application using `bin/rails react:build`, the whole application is code-split and deployed inside the Rails' `public` folder.
55+
When you build the React Router application using `bin/rails react_router:build`, the whole application is code-split and deployed inside the Rails' `public` folder.
5656
The table below shows the generated code-fragments.
5757

5858
Note that the code for each route has been split automatically, using information from the integrated router and without manual configuration.

0 commit comments

Comments
 (0)