Repository navigation
docs(mobile/4): skip Node setup for native starter kit - #489
Merged
simonhamp merged 1 commit intoSep 3, 2026
Merged
Conversation
simonhamp
approved these changes
Sep 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
--no-nodeto the Mobile v4 starter-kit commandWhy
The NativePHP Mobile starter uses native PHP/EDGE UI and does not ship with a Node or Vite asset pipeline. Laravel's default Node setup can therefore trigger an unnecessary
npm run buildstep, which fails because there is no Vite configuration or dependency to build.Passing
--no-nodecreates the starter in the form it is intended to run, giving new users a clean setup path without an irrelevant Node installation step.Validation
git diff --check