bundler uses different formatting for compared to `jspm install`

[atsu85]

Problem

bundler formats config.js differently compared to jspm install or update - git history is screwed. #54

Differences:

1) JSPM doesn't quote top-level keys in config. Result after jspm update

System.config({
  defaultJSExtensions: true,
  transpiler: "babel",
  babelOptions: {
    "optional": [
      "es7.decorators",
      "es7.classProperties"
    ]
  },

vs result after gulp bundle

System.config({
  "defaultJSExtensions": true,
  "transpiler": "babel",
  "babelOptions": {
    "optional": [
      "es7.decorators",
      "es7.classProperties"
    ]
  },

Suggestion

It would be nice if this format could be configured, so that git history would remain readable (without too much effort)

[EisenbergEffect]

@ahmedshuhel We should try to maintain the same formatting...

[ahmedshuhel]

@EisenbergEffect @atsu85 Ultimately, we are using JSON.stringify() to recreate the config file. I don't know if there is any way to tap into that function to change formatting. I will look into it. If that does not work we may have the change the whole implementation.

[EisenbergEffect]

@ahmedshuhel We should get in touch with @guybedford and ask why the serialization is that way. If he's using some 3rd party library to do that, we should use the same lib. But if that's somehow unintended, maybe we can all just use the standard stringify api.

[ahmedshuhel]

He is using something he wrote in jspm. I believe there is no third party library involved. I will raise an issue in jspm.

[ahmedshuhel]

Here is the issue I raised. https://github.com/jspm/jspm-cli/issues/1407

[ahmedshuhel]

The issue is fixed on the development branch. Will be included in the next release.