tommcc / grunt-eco Goto Github PK

I get this output:

npm http GET https://registry.npmjs.org/grunt-eco
npm http 200 https://registry.npmjs.org/grunt-eco
npm http GET https://registry.npmjs.org/grunt-eco/-/grunt-eco-0.1.1.tgz
npm http 200 https://registry.npmjs.org/grunt-eco/-/grunt-eco-0.1.1.tgz
npm http GET https://registry.npmjs.org/eco
npm http 200 https://registry.npmjs.org/eco
npm http GET https://registry.npmjs.org/eco/-/eco-1.0.3.tgz
npm http 200 https://registry.npmjs.org/eco/-/eco-1.0.3.tgz
npm http GET https://registry.npmjs.org/strscan
npm http GET https://registry.npmjs.org/coffee-script
npm http 200 https://registry.npmjs.org/strscan
npm http GET http://packages:5984/strscan/-/strscan-1.0.1.tgz
npm http 304 https://registry.npmjs.org/coffee-script
npm ERR! fetch failed http://packages:5984/strscan/-/strscan-1.0.1.tgz
npm http GET http://packages:5984/strscan/-/strscan-1.0.1.tgz
npm ERR! fetch failed http://packages:5984/strscan/-/strscan-1.0.1.tgz
npm http GET http://packages:5984/strscan/-/strscan-1.0.1.tgz
npm ERR! fetch failed http://packages:5984/strscan/-/strscan-1.0.1.tgz
npm ERR! network getaddrinfo ENOTFOUND
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network 
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'

npm ERR! System Darwin 13.0.0
npm ERR! command "/usr/local/Cellar/node/0.10.23/bin/node" "/usr/local/bin/npm" "install" "--save-dev" "grunt-eco"
npm ERR! cwd /Users/<user>/Code/project
npm ERR! node -v v0.10.23
npm ERR! npm -v 1.3.17
npm ERR! syscall getaddrinfo
npm ERR! code ENOTFOUND
npm ERR! errno ENOTFOUND
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/<user>/Code/project/npm-debug.log
npm ERR! not ok code 0

I can install other packages normally.

I had just made the change myself, and was forking the repo to create the PR, but then found the existing branch with commonJS support.

It seems to be pretty low-impact, code-wise--any chance of getting it merged? I could add documentation or tests if needed.

Please tag new version, so it can be fetched from NPM.

Grunt has been updated to version 1.0; are there any plans to make this package compatible with the newer version of grunt?

I'm posting this issue to let you know that we will be publishing Grunt 0.4 on Monday, February 18th.

If your plugin is not already Grunt 0.4 compatible, would you please consider updating it? For an overview of what's changed, please see our migration guide.

If you'd like to develop against the final version of Grunt before Monday, please specify "grunt": "0.4.0rc8" as a devDependency in your project. After Monday's release, you'll be able to use "grunt": "~0.4.0" to actually publish your plugin. If you depend on any plugins from the grunt-contrib series, please see our list of release candidates for compatible versions. All of these will be updated to final status when Grunt 0.4 is published.

Also, in an effort to reduce duplication of effort and fragmentation in the developer community, could you review the grunt-contrib series of plugins to see if any of your functionality overlaps significantly with them? Grunt-contrib is community maintained with 40+ contributors—we'd love to discuss any additions you'd like to make.

Finally, we're working on a new task format that doesn't depend on Grunt: it's called node-task. Once this is complete, there will be one more conversion, and then we'll never ask you to upgrade your plugins to support our changes again. Until that happens, thanks for bearing with us!

If you have any questions about how to proceed, please respond here, or join us in #grunt on irc.freenode.net.

Thanks, we really appreciate your work!

If someone wants to tackle this, please do. The tests seem to be broken in some non-obvious ways.

Let's say my Gruntfile config looks like

eco: {
  app: {
    src: ['<%= yeoman.app %>/scripts/views/**/*.eco'],
    dest: '<%= yeoman.tmp %>/scripts/views.js'
  }
}

The generated file then looks like

if (!window.JST) {
  window.JST = {};
}
window.JST["app/scripts/views/account/bar"] = function(__obj) {...}
window.JST["app/scripts/views/account/change_password"] = function(__obj) {...}
...

What I want is to have that instead:

if (!window.JST) {
  window.JST = {};
}
window.JST["account/bar"] = function(__obj) {...}
window.JST["account/change_password"] = function(__obj) {...}
...

So I'd like to set app/scripts/views as the basepath, so the the grunt tasks finds the files, but ignores the basepath in the JSTpaths.

I tried but couldn't figure out a way to do that.

Any idea? /cc @srigi