Relative paths with fetch in Javascript

I was surprised by an experience with relative paths in Javascript today. I’ve boiled down the situation to the following:

Suppose you have a directory structure like:


All my app.html does is run js/app.js

<!DOCTYPE html>
<script src=js/app.js></script>

app.js loads the JSON file and sticks it at the beginning of body:

// js/app.js
fetch('js/data.json') // <-- this path surprises me
  .then(response => response.json())
  .then(data => = data)

The data is valid JSON, just a string:

"Hello World"

This is a pretty minimal usage of fetch, but I am surprised that the URL that I pass to fetch has to be relative to app.html instead of relative to app.js. I would expect this path to work, since data.json and app.js are in the same directory (js/):

fetch('data.json') // nope

Is there an explanation for why this is the case?

7 thoughts on “Relative paths with fetch in Javascript”

  1. This is not exactly a recommendation since it relies on a number of things that aren’t guaranteed to work everywhere or to continue to work into the future, however it works for me in the places I need it to and it might help you.

    const getRunningScript = () => {
        return decodeURI(new Error().stack.match(/([^ \n\(@])*([a-z]*:\/\/\/?)*?[a-z0-9\/\\]*\.js/ig)[0])
    fetch(getRunningScript() + "/../config.json")
      .then(req => req.json())
      .then(config => {
        // code
  2. When you say fetch('data.json') you are effectively requesting since it is relative to the page your are making the request from. You should lead with forward slash, which will indicate that the path is relative to the domain root: fetch('/js/data.json'). Or fully quality with your domain fetch('').

  3. An easy way to understand why it must be the case is to consider what should happen if we write a helper function in app/js/helper/logfetch.js:

    // app/js/helper/logfetch.js
    function logFetch(resource) {
        console.log('Fetching', resource);
        return fetch(resource);

    Now, consider what happens if we use logFetch from app/js/app.js:

    // app/js/app.js
    fetch('data.json');    // if this is relative to js/, then ...
    logFetch('data.json'); // should this be relative to js/ or js/helper/?

    We might want these two calls to return the same thing – but if fetch is relative to the contained file, then logFetch would request js/helper/data.json instead of something consistent with fetch.

    If fetch could sense where it is called from, then to implement helper libraries such as logFetch, the JavaScript would need a whole range of new caller-location-aware functionality.

    In contrast, performing the fetch relative to the HTML file provides more consistency.

    CSS works differently because it doesn’t have the complexity of method calling: you can’t create "helper CSS modules" that transform other CSS modules, so the idea of relative paths is a lot more conceptually cleaner.

  4. Update 2021


    class Path{
            this.arr = path.split('/');
            return this.arr.join('/');
            return new Path(this.arr.join('/'));
            for(let ii = 0; ii < n; ii++){
            return this;
            if(arr_or_str instanceof Array){
                // string
            return this;
    /* e.g.
    localhost/8888/test/index.js   backward   localhost/8888/test/
    localhost/8888/test/  forward('index.js') localhost/8888/test/index.js
    localhost/8888/ forward(['db', 'course.json']) localhost/8888/db/course.json
    // for example, I want to fetch `db/course.json` in current directory
    fetch(new Path(window.location.href).backward(1).forward(["db", "calendar.json"]).url())
        .then(res => {

    if the string did not match the expected pattern occurs, refer to this SO post


Leave a Comment