You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+10-1Lines changed: 10 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,7 @@ These projects were the main inspiration for creating this starter kit. I’ve a
44
44
45
45
I prefer explicit event handling over “magic” behavior. With custom events, you can keep logic clean and encapsulated inside dedicated listener classes.
46
46
47
-
6.**Custom Helpers**: Instead of a typical `helpers.php` file, this kit organizes helpers as **Traits**, **Services**, **Support** classes, and **Facades**.
47
+
6.**Custom Helpers**: This kit organizes helpers as **Traits**, **Services**, **Support** classes, and **Facades**.
48
48
- A small `helpers.php` file is still included for global functions where class imports aren’t possible.
49
49
50
50
---
@@ -111,6 +111,15 @@ Now as the app is all setup correctly you can start working on it:
111
111
composer dev
112
112
```
113
113
114
+
**Note**: `composer dev` may give you an error about the `pail` command, specially on Windows machines, as the `pail` command is not supported on windows.
115
+
116
+
To make it work you can use alternative command:
117
+
118
+
```bash
119
+
# Start development server on Windows
120
+
composer dev:win
121
+
```
122
+
114
123
### Check on browser
115
124
116
125
After running your development server you can visit to [http://localhost:8000](http://localhost:8000) or [http://127.0.0.1:8000](http://127.0.0.1:8000) on your favorite browser to see the app in action.
0 commit comments