[5.4] while doing 'npm run hot', do not require existence of the manifest file for 'mix()' #18088
Conversation
This file contains 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
rhyek
changed the title
npm run hot, do not require existence of the manifest filenpm run hot, do not require existence of the manifest file for mix()
rhyek
changed the title
npm run hot, do not require existence of the manifest file for mix()
themsaid
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
With tested versions of
laravel-mix, the manifest file isn't generated when runningnpm run hot. This makes it so you need to runnpm run dev, for example, before runningnpm run hoteither on first run or every time a new file should exist.