Hey Ramiro,
What you report is true, I just went through this myself setting up a new Spine app.
You'll need to edit the package.json that Spine.app provides.
Additionally, I needed this change to jqueryify for it to work:
The above is the minimal you'll need to get things working.
----
But I ended up not liking that solution and ended up doing the following...
package.json dependences:
"dependencies": {
"spine": "~1.3.0",
"hem": "~0.3.6"
}
Here I reduced the npm module dependencies.
If you need to support browsers older than IE9 you'll want to keep es5-shimify, json2ify as dependencies here.
bower.json dependencies:
"dependencies": {
"jquery": "~2.1.0"
}
Here I moved the jquery dependency to be managed by bower b/c the jqueryify module wasn't exporting jQuery correctly.
slug.json packages.appName.libs packages.appName.modules:
"packages": {
"appName": {
"libs" : [
"lib/runtime.js",
"bower_components/jquery/dist/jquery.min.js"
],
"modules" : [
"spine",
"spine/lib/local",
"spine/lib/ajax",
"spine/lib/route",
"spine/lib/manager"
]
And here I updated libs to include jquery from my bower_components.
I included modules here as well as you probably want to add local (LocalStorage), ajax (Ajax server communication), and manager (for Stack) here.
You'll need to update app/lib/setup.coffee to reflect the modules in slug.json:
I found having app/lib/setup.coffee a bit odd and ended up moving the require statements from setup.coffee to my main app/index.js (which I renamed app/app.js).
----
NOTE: while this is my current setup I plan to try replacing hem with gulp and browserify and only use npm to manage packages removing the need for bower.
----
Hope this helps. Let me know how it goes. The Spine.app templates should get updated at least to something to works out of the box. Luckily I used Spine before and knew my way around a bit. ;)
-r.