Fetch packages from jspm.dev instead of dev.jspm.io?

[jneurock]

Hi,

I've noticed some interesting package contents coming from https://dev.jspm.io and some libraries have failed to load dependencies without error. I also noticed that package contents are different from https://jspm.dev.

---

Failing Example:

// Pulls from `https://dev.jspm.io/@mirage/graphql`
import { createGraphQLHandler } from "@mirage/graphql"

The Mirage GraphQL package loads but it depends on GraphQL JS which fails to load correctly.

---

Working Example:

import { createGraphQLHandler } from "https://jspm.dev/@miragejs/graphql"

This works just fine but the package contents seem quite different from what's fetched from https://dev.jspm.io.

---

This all leads to a few questions:

• Why would the first example fail?
  • I'm totally open to the problem being on the Mirage GraphQL side. If that's the case, any help getting that figured out would be very appreciated.
• Why not pull packages from https://jspm.dev?
• Could a solution be that the CDN_ESM_URL constant be overridable with a config option?

Thanks in advance!