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: DEVELOPMENT.md
+16-4Lines changed: 16 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,10 +60,6 @@ Typically, packages listed in this section would be internal development tools f
60
60
- PHPStan
61
61
- Codeception
62
62
63
-
### Build
64
-
65
-
Run `npm run build` to compile frontend CSS and JS in one step.
66
-
67
63
### CSS
68
64
69
65
Run `npm run watch:css` to compile frontend CSS to `resources/frontend/css/frontend.css` when working on SCSS in the `resources/frontend/scss` folder.
@@ -72,6 +68,22 @@ Run `npm run watch:css` to compile frontend CSS to `resources/frontend/css/front
72
68
73
69
Run `npm run watch:js` to compile frontend JS to `resources/frontend/js/dist/frontend-min.js` when working on JS in the `resources/frontend/js` folder.
74
70
71
+
### Build
72
+
73
+
Run `npm run build` to:
74
+
- fix CSS to WordPress Coding Standards (`npm run fix:css`)
75
+
- lint CSS to check WordPress Coding Standards met after any fixes (`npm run lint:css`)
76
+
- fix JS to WordPress Coding Standards (`npm run fix:js`)
77
+
- lint JS to check WordPress Coding Standards met after any fixes (`npm run lint:js`)
78
+
- compile frontend CSS from `resources/frontend/scss` to `resources/frontend/css/frontend.css` (`npm run build:css`)
79
+
- compile frontend JS from `resources/frontend/js` to `resources/frontend/js/dist` (`npm run build:js`)
80
+
81
+
If the build process fails, review the terminal and make applicable changes:
82
+
83
+

84
+
85
+
GitHub actions will run this step for you on testing and deployment, but it's a useful command in development if you need a single command to cover CSS + JS.
86
+
75
87
## Committing Work
76
88
77
89
Remember to commit your changes to your branch relatively frequently, with a meaningful, short summary that explains what the change(s) do.
0 commit comments