We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Let's consider using WP scripts as build process example. This would replace Gulp.
General idea is that if there is a tool from WP project, let's at least test.
It is also possible to handle all builds from the root of the project using NPM workspaces.
This might need separate "seravo-example-project" showcasing the idea.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Let's consider using WP scripts as build process example. This would replace Gulp.
General idea is that if there is a tool from WP project, let's at least test.
Run build from root for all assets
It is also possible to handle all builds from the root of the project using NPM workspaces.
This might need separate "seravo-example-project" showcasing the idea.
The text was updated successfully, but these errors were encountered: