500 Error on submitting 'Elm'

[pastelsky]

500 Error on submitting 'Elm'

[pastelsky]

The package you're referring to is a npm wrapper over platform binaries primarily written in languages other than JS. Building this is out of scope for this project.

[sleepyfox]

Maybe remove it from the list then?

[pastelsky]

Which list are you referring to?

[sleepyfox]

I was referring to the list of packages, but I assume you're just deferring that search to npm. It would be nice to at least catch the packages that stall in 'checking files sizes' due to native dependencies and putting up a user-friendly error message along the lines of "Cannot calculate file size due to native code dependencies" or something similar.

…

On 13 October 2017 at 13:15, Shubham Kanodia ***@***.***> wrote: Which list are you referring to? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[pastelsky]

There isn't currently a general way to detect that I'm afraid.

…

On 13-Oct-2017 6:41 PM, ***@***.***" ***@***.***> wrote: I was referring to the list of packages, but I assume you're just deferring that search to npm. It would be nice to at least catch the packages that stall in 'checking files sizes' due to native dependencies and putting up a user-friendly error message along the lines of "Cannot calculate file size due to native code dependencies" or something similar. On 13 October 2017 at 13:15, Shubham Kanodia ***@***.***> wrote: > Which list are you referring to? > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub, or mute the thread. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#21 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIiCH4jSoQc4Duexx_BbN1a7lOx50wdtks5sr2FzgaJpZM4PwtZW> .

[OmgImAlexis]

@pastelsky I'm guessing this means any builtins like path, url, etc?

Also getting the same error with medusa-lib but I don't use any builtin packages.

[pastelsky]

@OmgImAlexis The error in medusa-lib is due to it using es2017 features (spread operators) in it's entry point. We support only limited transpilation of npm packages (only features supported by uglify-es) and either way, it's a best practice to transpile your code before publishing it to npm.

Please feel free to open a new issue if you've any queries about this.