Dynamic languages don't generally favor using a function/class over a plain-old-struct, so there's no conceptual advantage to calling

  class GetNoCacheDefaultCookieJarStrategy {
    ...
  }
  fetch('https://google.com', new GetNoCacheDefaultCookieJarStrategy())

over

  const my_usual_fetch_opts = {...}
  fetch('https://google.com/', my_usual_fetch_opts)

There are almost no uses of the strategy pattern that aren't equivalent to a trivial first-class function like a filter predicate or equivalent to a trivial plain-old-key-value-options-object, so the non-pattern version is stylistically preferred in the 99% case where it's not actually necessary.