jharding / grunt-sed Goto Github PK

Error while executing:
npm ERR!
/usr/bin/git ls-remote -h -t ssh://[email protected]/twbs/grunt-sed.git

the username is incorrect

So, I dug in a bit. It appears to be basically running a sed -i command, replacing the current file with the updates.

Is it possible have an output file so that I can write the file to a different place?

It would be nice if sed allow to use wildcards and other goodies available in most of grunt tasks (http://gruntjs.com/configuring-tasks#globbing-patterns), for example:

sed:
    all_api_url:
        path: "build/**/*.{js,html}"
        pattern: '%API%'
        replacement: "<%= config.api_url %>"

For now it fails: Warning: ENOENT, no such file or directory.

How to ignore node_modules directory when run sed?

I was working on a minor change to cleanup generated source maps and used grunt-sed at first but had to switch after noticing that it was only replacing the first instance of a string on a line. I tried using /foo/g instead of a string pattern to no effect

Hey, it would be great if it supported multiple build phases. Development, Staging, Product, etc...

I tend to have specific replacements that happen for different phases of development/deployment and would really like to take it out of my node app and put it into Grunt.

If I end up with some free time, maybe I can help contribute a potential solution for something like this - but figured I'd toss it out there.

Thanks!!

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!