Kumar McMillan

Is this still happening? If I could see a verbose log it would be helpful

Thanks for the log. I think this is an eventual consistency issue. We use Amazon S3 to store files so what may be happening is that the file is not...

Could you try reproducing this? If you were experiencing https://github.com/mozilla/web-ext/issues/1111 then we pushed a fix to the signing API which should address it. However, if your bug is entirely related...

@jeffesquivels yes, thanks for digging into this! I looked at your linked commit but I couldn't find a pull request for it. I think you are on the right path...

I was talking about `web-ext run --verbose` which shows all Firefox errors. It should only show errors related to the extension you are running. Working on this feature might be...

It's also possible that using the extension debugger would be better than this (because I think the debugger can show only errors related to the extension?). Maybe we need to...

Hi @karuppiah7890 , that's great! This is a big patch and will require a lot of work. I don't want to dissuade you but I would suggest starting with some...

btw, the [yeoman](http://yeoman.io/) project would probably be a good framework to use for the `new` command.

@andymckay left this comment on https://github.com/mozilla/web-ext/issues/141 There are a few projects that kind of do this already: - https://github.com/yeoman/generator-chrome-extension - http://extensionizr.com/ There are probably more, would it make sense to...

> as an npm/jpm user I think we should at least alias init to new Sure, we could add a hidden alias. It probably makes sense to put a page...