<p dir="auto">If I have <code class="notranslate">/pages/one/index.js</code>, the URL <code class="notranslate">/one</code> resolves to the <code class="notranslate">index.js</code>. Great.</p>
<p dir="auto">But if I have <code class="notranslate">/pages/one/two/index.js</code>, the URL <code class="notranslate">/one/two</code> does <em>not</em> resolve to <code class="notranslate">index.js</code>. I get <code class="notranslate">error: Cannot GET /one/two</code>. The URL <code class="notranslate">/one/two/index.js</code> does not work either, as I'd expect.</p>
<p dir="auto">I think nesting like this should work.</p>
<p dir="auto">Hello!</p>
<p dir="auto">I have a dependency in my application that specifically relies on <code class="notranslate">window.fetch</code> being replaced with the whatwg-fetch polyfill. whatwg-fetch is a transitive dependency, so it should be ending up in my build, but it looks like next.js is replacing it with something else.</p>
<p dir="auto">From reading the docs it seems like next provides it's own fetch polyfill? Does that sound right, or am I totally off track here?</p>
<p dir="auto">Thanks!</p>