Use CLI to provide JSPM-like functionality?

[robwormald]

One of the reasons SystemJS has a lot of boilerplate is that it's really designed for a case where the jspm CLI is managing your config.js file automatically for you. When somebody uses regular NPM, they don't get this automatic config and thus there's a lot of manual mapping that has to be done, eg:

System.config({
 map: {
 'angular2': 'node_modules/angular2',
 'my-super-awesome-lib' : 'node_modules/my-super-awesome-lib'
 },
 packages: {
 'my-super-awesome-lib': {
 'main': 'index.js'
 }
 }
})

This gets unwieldy fast and is super complicated if you don't know the System config API very well. It seems like this could be handled with our CLI, especially given the stuff you're doing with adding providers and stuff.

Thoughts?

[hansl]

I'm working on a design doc for ng install that will cover this. We will get a simpler System.config for the user (and he can still customize it).

The magic bits will be moved to a file that we control, and the user just need to include/import that file.

[timkindberg]

Yes I'd say this issue is strongly related (if not a duplicate of) #124 and I also highly agree this needs to be a thing. +1

[khanhhua]

+1 This is super urgent. It's likely we abandon that CLI if I have to manually config for SystemJS for every node_module package.

[zackarychapple]

Giant +1 here too.

[hansl]

@khanhhua: the tool is not even in Alpha and you shouldn't use this for any serious projects (yet).

The proposal is under way and we'll configure SystemJS properly once we're done with it.

See the design doc here: #255

Closing this as a duplicate.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}