added can parameter

[gsmeets]

can.view.parser is set at the end of the file. The dependency can is
not imported, this causes issues during AMD optimization, because the
reference can at that point doesn't exist through window.can, as it
does in the browser.

[gsmeets]

Hmm, seems like I'm running into some more of these issues. I'll add those to this pull request once I've fixed them..

[gsmeets]

I've added another can import for view/stache/stache.js. Now I got stache precompiled templates running on node. I've imported can/util/library.js for lack of a better candidate. Doesn't seem to matter that much, as long as there's some prototype to extend that will be picked up later by other components.

[justinbmeyer]

It should not be can. That forces a dependency on everything in core. It should be 'can/util'.

Sent from my iPhone

On May 12, 2014, at 5:10 PM, Guido Smeets notifications@github.com wrote:

I've added another can import for view/stache/stache.js. Now I got stache precompiled templates running on node. I've imported can/util/library.js for lack of a better candidate. Doesn't seem to matter that much, as long as there's some prototype to extend that will be picked up later by other components.

—
Reply to this email directly or view it on GitHub.

[gsmeets]

To clarify, for can/view/parser I just added a parameter name for the already imported can/view. For can/view/stache/stache I added can/util/library as a reference. Both imports are named can locally.

(p.s. Travis reports failed builds. Is that due to my changes? Seems unlikely to me.)

[justinbmeyer]

can/util/library should be can/util.

[justinbmeyer]

the can/util/library might have broken it.