Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Can't resolve paths from index.html after npm run build
See original GitHub issueAfter building an app into /dist folder index.html references all resources (minified .css, .js and images) as /resource_name instead of ./resources_name. Manually replacing / to ./ in webpack.config.prod.js:output.publicPath or in index.html fixes the problem.
Am I doing something wrong that I have to do it manually?
P.S. The issue does not affect the dist server.
Node version: 6.9.2
npm version: 3.10.9
Operating system: macOS 10.12.3
Command line used: npm run build (excluded linting and testing)
Steps to reproduce: npm run build
Issue Analytics
- State:
- Created 6 years ago
- Comments:12 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I created a short note in FAQ on this topic.
I agree that a deploy section would be useful, and likely expose us to opportunities for improvement. I’d welcome a related PR.