The latest articles on DEV Community by Chris Shaffer (@methodbox). https://dev.to/methodbox https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F193300%2F0651603b-c232-41c5-bef8-bc3f7ae3ff79.jpeg https://dev.to/methodbox en Chris Shaffer Thu, 19 Dec 2019 16:19:30 +0000 https://dev.to/methodbox/webpack-remote-development-1i2c https://dev.to/methodbox/webpack-remote-development-1i2c <p>I didn't want my first post on Dev.to to be a question, but it seems to be the best place I've found to answer many other questions, so here goes.</p> <p>I'm working on an app that requires I access an iframe; this means due to <code>same-origin</code> policy it would be awesome if I could do remote dev on the server providing the iframe so the origin is the same.</p> <p>Right now, I'm running a build, uploading it to the test server, then messing with testing with the iframe in the browser console.</p> <p>I'm wondering if anyone has had any success and can provide specific guidance on configuring Webpack to work with Nginx on a <em>non-web root</em> URL (i.e domain.com/testing).</p> <p>I can get webpack to run, and I have a proxy_pass in Nginx successfully serving the page, however Webpack refuses to serve the app (Cannot GET /testing).</p> <p>I've tried various configurations of the <code>publicPath</code>, <code>public</code> and <code>contentBase</code> settings, but Webpack simply can't figure out that I'm not at the web root. The console shows 404s for various scripts looking at <code>/</code> instead of <code>/testing</code>. None of this changes with the various <code>devServer</code> configs.</p> <p>Any help would be greatly appreciated.</p> webpack question javascript