Updated the rootPath to the working directory of the node process. #1719
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.
Currently laravel-mix breaks when your
node_modules
directory is a symlink. This is due to the fact that relatives paths don't work when you are using a symlink because they will not point to your project root but will rather move relative to where your symlinked files are located.A symlinked
node_modules
directory is pretty common when using a project with continuous integration where you are building on a production server. Examples of this are codeship or envoyer. When you are symlinking yournode_modules
directory you are not forced to rebuild it for every deploy which saves a lot of time and resources.The documentation on process.cwd():
https://nodejs.org/docs/latest/api/process.html#process_process_cwd
This should help fix:
#533
#650
#664
With this update the relative paths are completely removed and symlinks work perfectly fine.
I would love to get more input from more experience Node.js users on this request to see if this can lead to any potential drawbacks.