Set up Laravel as an API backend by installing Laravel, configuring the database, creating API routes, and returning JSON from controllers, optionally using Laravel Sanctum for authentication. 2. Choose between a standalone React SPA served separately or using Inertia.js for tighter Laravel integration, with Inertia allowing React components to work within Laravel’s routing and session system. 3. When using Inertia, install the required packages, configure Vite, create a root React component, place React pages in resources/js/Pages/, and return Inertia responses from routes with data passed as props. 4. For a decoupled setup, run Laravel and React on separate domains, use Axios or Fetch to call Laravel APIs from React, and handle CORS and authentication properly. 5. Best practices include using Vite for faster builds, organizing React components by feature, formatting API responses with Laravel API resources, and testing CORS and authentication early. The choice between Inertia and a standalone React app depends on project complexity and team preferences, with Inertia simplifying full-stack integration and standalone SPAs offering greater frontend flexibility, both valid approaches for modern Laravel-React applications.
Integrating React with Laravel allows you to build powerful, dynamic frontends while leveraging Laravel’s robust backend features like routing, authentication, and APIs. Here’s how to do it effectively in a modern Laravel project.

1. Set Up Laravel and Create an API
First, make sure Laravel is set up to act as a backend API.
-
Install Laravel via Composer:
composer create-project laravel/laravel your-project-name
Configure your
.env
file with database settings and run migrations:php artisan migrate
Create API routes in
routes/api.php
:Route::get('/posts', [PostController::class, 'index']);
Ensure your controllers return JSON (API resources or Eloquent collections):
public function index() { return Post::all(); }
Use Laravel Sanctum if you need authentication for your React frontend.
2. Choose How to Serve React: SPA vs Inertia.js
You have two main approaches:
Option A: Standalone React App (SPA)
- Build React separately using Vite or Create React App.
- Serve it from a different domain (e.g.,
http://localhost:3000
) or as static files. - Configure Laravel to proxy API calls during development (optional).
? Best for large, complex frontends with many interactive components.
Option B: Use Inertia.js (Recommended for Simplicity)
Inertia lets you use React components while staying within Laravel’s routing and session system.
Install Inertia:
composer require inertiajs/inertia-laravel
Set up frontend scaffolding:
npm install @inertiajs/react react react-dom @vitejs/plugin-react
Update
vite.config.js
:import { defineConfig } from 'vite'; import react from '@vitejs/plugin-react'; import laravel from 'laravel-vite-plugin'; export default defineConfig({ plugins: [ laravel({ input: 'resources/js/app.jsx', refresh: true, }), react(), ], });
Create your root React component (
resources/js/app.jsx
):import { createRoot } from 'react-dom/client'; import { createInertiaApp } from '@inertiajs/react'; createInertiaApp({ resolve: name => require(`./Pages/${name}`), setup({ el, App, props }) { createRoot(el).render(<App {...props} />); }, title: title => `My App | ${title}`, });
Return Inertia responses from Laravel routes:
use Inertia\Inertia; Route::get('/', function () { return Inertia::render('Welcome', ['message' => 'Hello from Laravel!']); });
? Great for full-stack apps where you want Laravel handling routing and React powering the UI.
3. Build React Components Inside Laravel
With Inertia or a bundled setup:
Place React components in
resources/js/Pages/
.Example:
resources/js/Pages/Posts/Index.jsx
import { usePage } from '@inertiajs/react'; export default function PostIndex({ posts }) { const { props } = usePage(); return ( <div> <h1>Posts</h1> {props.posts.map(post => ( <div key={post.id}>{post.title}</div> ))} </div> ); }
Pass data from Laravel controller:
return Inertia::render('Posts/Index', [ 'posts' => Post::all() ]);
? For dynamic data (e.g., search, pagination), use Inertia visits or Axios to hit Laravel API routes.
4. Use Laravel as API React as Frontend (Decoupled)
If you prefer a fully separate frontend:
Keep Laravel running on
api.yourapp.test
(backend only).Build React app (using Vite, Next.js, etc.) on
localhost:3000
.Call Laravel APIs via Axios or Fetch:
useEffect(() => { axios.get('http://api.yourapp.test/api/posts') .then(res => setPosts(res.data)) .catch(err => console.error(err)); }, []);
Handle CORS: Install
fruitcake/laravel-cors
or use Laravel Sanctum’s SPA features.composer require fruitcake/laravel-cors
?? Remember to manage authentication (Sanctum/Socialite) and CSRF if not stateless.
Final Tips
- Use Vite over Webpack (faster builds).
- Keep React components organized by page or feature.
- Use Laravel API resources to format JSON output cleanly.
- Test CORS and authentication early.
Basically, you can either tightly couple React via Inertia or keep it separate as a frontend SPA. Inertia reduces complexity and keeps you in the Laravel ecosystem, while a standalone React app gives more frontend flexibility. Choose based on your team and project needs.
The above is the detailed content of How to integrate React with Laravel?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

1. The first choice for the Laravel MySQL Vue/React combination in the PHP development question and answer community is the first choice for Laravel MySQL Vue/React combination, due to its maturity in the ecosystem and high development efficiency; 2. High performance requires dependence on cache (Redis), database optimization, CDN and asynchronous queues; 3. Security must be done with input filtering, CSRF protection, HTTPS, password encryption and permission control; 4. Money optional advertising, member subscription, rewards, commissions, knowledge payment and other models, the core is to match community tone and user needs.

This article aims to resolve common errors in the Laravel framework where routing parameter passing matches controller methods. We will explain in detail why writing parameters directly to the controller method name in the routing definition will result in an error of "the method does not exist", and provide the correct routing definition syntax to ensure that the controller can correctly receive and process routing parameters. In addition, the article will explore best practices for using HTTPDELETE methods in deletion operations.

When choosing a suitable PHP framework, you need to consider comprehensively according to project needs: Laravel is suitable for rapid development and provides EloquentORM and Blade template engines, which are convenient for database operation and dynamic form rendering; Symfony is more flexible and suitable for complex systems; CodeIgniter is lightweight and suitable for simple applications with high performance requirements. 2. To ensure the accuracy of AI models, we need to start with high-quality data training, reasonable selection of evaluation indicators (such as accuracy, recall, F1 value), regular performance evaluation and model tuning, and ensure code quality through unit testing and integration testing, while continuously monitoring the input data to prevent data drift. 3. Many measures are required to protect user privacy: encrypt and store sensitive data (such as AES

There are three main ways to set environment variables in PHP: 1. Global configuration through php.ini; 2. Passed through a web server (such as SetEnv of Apache or fastcgi_param of Nginx); 3. Use putenv() function in PHP scripts. Among them, php.ini is suitable for global and infrequently changing configurations, web server configuration is suitable for scenarios that need to be isolated, and putenv() is suitable for temporary variables. Persistence policies include configuration files (such as php.ini or web server configuration), .env files are loaded with dotenv library, and dynamic injection of variables in CI/CD processes. Security management sensitive information should be avoided hard-coded, and it is recommended to use.en

To enable PHP containers to support automatic construction, the core lies in configuring the continuous integration (CI) process. 1. Use Dockerfile to define the PHP environment, including basic image, extension installation, dependency management and permission settings; 2. Configure CI/CD tools such as GitLabCI, and define the build, test and deployment stages through the .gitlab-ci.yml file to achieve automatic construction, testing and deployment; 3. Integrate test frameworks such as PHPUnit to ensure that tests are automatically run after code changes; 4. Use automated deployment strategies such as Kubernetes to define deployment configuration through the deployment.yaml file; 5. Optimize Dockerfile and adopt multi-stage construction

This article deeply explores the correct transmission of routing parameters and the matching mechanism of controller methods in the Laravel framework. In response to the common "method does not exist" error caused by writing routing parameters directly to the controller method name, the article elaborates on the correct way to define routing, that is, declare parameters in the URI and receive them as independent parameters in the controller method. At the same time, the article also provides code examples and suggestions on best practices for HTTP methods, aiming to help developers build more robust and RESTful Laravel applications.

To build a PHP content payment platform, it is necessary to build a user management, content management, payment and permission control system. First, establish a user authentication system and use JWT to achieve lightweight authentication; second, design the backend management interface and database fields to manage paid content; third, integrate Alipay or WeChat payment and ensure process security; fourth, control user access rights through session or cookies. Choosing the Laravel framework can improve development efficiency, use watermarks and user management to prevent content theft, optimize performance requires coordinated improvement of code, database, cache and server configuration, and clear policies must be formulated and malicious behaviors must be prevented.

Laravel's EloquentScopes is a tool that encapsulates common query logic, divided into local scope and global scope. 1. The local scope is defined with a method starting with scope and needs to be called explicitly, such as Post::published(); 2. The global scope is automatically applied to all queries, often used for soft deletion or multi-tenant systems, and the Scope interface needs to be implemented and registered in the model; 3. The scope can be equipped with parameters, such as filtering articles by year or month, and corresponding parameters are passed in when calling; 4. Pay attention to naming specifications, chain calls, temporary disabling and combination expansion when using to improve code clarity and reusability.
