[extension-upload] - unable to upload a brackets extension to the registry

[timoweiss]

Hey, tried to upload an extension to the registry but i always get the following error:
"The extension package is invalid: The uploaded content is not a valid zip file."

My zip file has a size of about 3.1Mb.
It has a main.js and a valid package.json.
I have the suspicion that the large amount of files cause the error. Is it possible that there is any limit?

I created the zip via terminal 'zip requireRelease.zip . -r'

See also: https://groups.google.com/forum/#!topic/brackets-dev/srV4w5O0r94

[dangoor]

I was able to upload the file on localhost.

@ingorichter is there something in the log on the server perhaps?

[timoweiss]

@ingorichter any news?

[pthiess]

Doesn't seem to impact many people, hence marking it low priority to investigate @ingorichter.

[peterflynn]

Note: @timoweiss mentioned in the forum that removing "font-awesome" from his set of NPM modules fixes this. I wonder if there's anything unusual inside that folder structure that we're choking on? (Or does it just reduce the number of files / depth of nesting dramatically?)

[timoweiss]

i was just about to write here :)

here's the file-tree of font-awesomes node_modules dir:

-node_modules
|---less
|-----benchmark
|-----bin
|-----build
|-----dist
|-----lib
|-------less
|---------tree
|-----node_modules
|-------mime
|---------types
|-------mkdirp
|---------examples
|---------test
|-------request
|---------lib
|---------node_modules
|-----------aws-sign2
|-----------forever-agent
|-----------form-data
|-------------lib
|-------------node_modules
|---------------async
|-----------------lib
|---------------combined-stream
|-----------------lib
|-----------------node_modules
|-------------------delayed-stream
|---------------------lib
|---------------------test
|-----------------------integration

[ingorichter]

@timoweiss @dangoor I'm sorry, but there was nothing in the logfiles that provides more information to resolve this issue.

[peterflynn]

@ingorichter Now that we know the "font-awesome" NPM package was the culprit, should we try reproducing it ourselves using a fake extension that includes that package?

[ingorichter]

@peterflynn Yes, I'm going to do this.

[timoweiss]

@ingorichter sorry, i couldn't wait, i tried it. And the upload was successful. But i had to remove some files from the node_module less to achieve the 5Mb. So, could you please remove my test-extension called font-awful from the registry.
Its maybe not font-awesome which caused the problem, but it might be the mass of files.
Thank you.

[peterflynn]

@timoweiss You should be able to remove it yourself now -- we've just updated the registry, and you should now see a Delete button next to any extensions you own.

[timoweiss]

@peterflynn perfect, it worked! Thanks!