debug@2.6.0 override not working

[perrin4869]

I did:

rm ~/.jspm
jspm uninstall debug
jspm install debug

Inside a jspm project, however, the following is obtained:

$ cat jspm_packages/npm/debug@2.6.0.json                                                                                                                                 
{
  "main": "browser.js",
  "format": "cjs",
  "map": {
    "./browser.js": {
      "node": "./node.js"
    },
    "fs": "@node/fs",
    "net": "@node/net",
    "tty": "@node/tty",
    "util": "@node/util"
  }
}

which is not the override defined in this repository here

What could be the problem? Thanks!

[aluanhaddad]

Do you have an existing override? Try jspm install npm:debug --force

[guybedford]

jspm install npm:debug -fo can also be used here to force update the override from the original override as well.

[perrin4869]

I see! Yeah the problem was the override inside the package.json... maybe it'd be a good idea to make -fo a default?

[guybedford]

The -o option is basically just to reset to an empty override. By default the existing override is maintained to ensure that once you install with an override it doesn't change. That is necessary to keep installs consistent.

[perrin4869]

hm... why add the segment to package.json when doing jspm install npm:debug then?

[guybedford]

That is exactly the override - the override used at install time is stored as a constant of the build so that subsequent installs are complete replications.

[perrin4869]

hm... what about the cases where it's not constant? It seems to me like the override section in package.json should be reserved for manual overrides only, while overrides that come from the registry should remain in jspm.config.js only, since they may change during upgrade

[guybedford]

This is what we did in jspm 0.16, but changed this in 0.17 because otherwise registry overrides can never be changed without breaking someone's build (which happened a few times before).

[perrin4869]

hm... I fail to see how that would break someone's build. If they are relying on the registry's overrides, and the registry override is updated correctly, how could the build break?

[guybedford]

Most override changes are backwards-incompatible.

[perrin4869]

hm... I think I need an example to figure this one out. Anyways, this issue is solved now, thanks!