Include requirejs and requirejs/text via NPM.

[shaunluttin]

Right now these are included in the scripts directory instead of letting NPM install them.

In the aurelia.json, please move from this:

"prepend": [                                                   
  "scripts/require.js"                                         
],                                                             
"dependencies": [                                              
{                                                            
  "name": "text",                                            
  "path": "../scripts/text"                                  
},                                                           

to this:

"prepend": [                                                   
  "node_modules/requirejs/require.js"                          
],                                                             
"dependencies": [                                              
  "text",                                                      

And add this to the package.json dependencies

"requirejs": "^2.3.2",
"text": "github:requirejs/text"

[EisenbergEffect]

Sounds reasonable :) Is it not possible to get require.js from npm?

[shaunluttin]

Yes. It is possible to get require.js from NPM. It is also possible to get requirejs/text from there too. The problem is that the aurelia-cli scaffolding does not do that, so we have to manually make the above changes.

[gheoan]

Note that the text plugin is not in the npm registry, but can be obtained from github via npm. requirejs/text#122

[AStoker]

Many of the people I've talked to have already replaced the included require and text loaders with the ones from npm. It seems simple enough to do and probably worth doing. Just have to modify the default aurelia.json file to load up those files, and include them in the default package.json

[shaunluttin]

Many of the people I've talked to have already replaced the included require and text loaders with the ones from npm.

@AStoker That's what I do too. For one, it's a pain. For two, it's an inconsistent message to people learning Aureila; i.e. why are some libraries pulled from NPM but others placed in scripts, and thereby also in version control? I still don't know the answer.

It seems simple enough to do...

I hope you mean that it is simple enough for the Aurelia-CLI team and that you will do it. If you mean simple enough for users of Aurelia, then I for one can say that I did not find it simple to do.

[EisenbergEffect]

I think we should fix this. It shouldn't be hard.

[AStoker]

@EisenbergEffect, how does this look: #391