Bug Fix: Webpack publicPath output configuration was updated to auto.… #13
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.
… Previous value of "./" was causing build issues.
References
#10
Description
When running NPM start or NPM build, the output publicPath value of "./" was causing an issue where the route could not be found. However, this issue wouldn't have been seen in the build, since index.html would be in the same folder as the script files. Changing publicPath to "auto" fixed both use cases.
Validation performed