Should I commit `config.js` and `jspm_packages` into repository? about registry HOT 1 CLOSED

Glad to hear you are trying it out. Responses below:

On Friday, November 28, 2014, Thai Pangsakulyanont [email protected]
wrote:

I'm experimenting with jspm.io. I have some questions:

• I'd like to know if config.js and/or jspm_packages should be
  commited to the repository or not.

config.js should be checked in but not jspm_packages

• I prefer not to commit jspm_packages to the repository, with similar
  reason for node_modules.
• If I commit only config.js, I'm not sure if when someone else check
  out the code, and type jspm install, will config.js stay the same or
  not. If config.js is so constantly updated, I prefer not to put
  config.js inside source tree.

In the latest [email protected] which will be released as stable very soon,
'jspm install' guarantees fully-reproducible installs from Config.js.

But config.js also contains some custom configuration such as custom
mapping for SystemJS plugins:

"jsx": "app/transformers/jsx",

- When I put the "map" key in package.json, delete config.js, and run jspm

install, the "map" key I specified in the JSON does not show up inside
the generated config.js.

This was implemented previously, there's an issue to add this back and
contributions are welcome too.

• So, is config.js meant to be edited by human or the CLI?

Both! You can add any of your own custom properties or configs and they
will be preserved. You can also alter the version resolutions or endpoint
paths. If you alter a version resolution outside of its allowed range, jspm
will not try to update or change it. Aiming to tackle all the edge cases
along these lines.

Reply to this email directly or view it on GitHub
#77.

from registry.