Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Serverless deploy errors out. #1701

Closed
Jorenm opened this issue Jul 28, 2016 · 2 comments
Closed

Serverless deploy errors out. #1701

Jorenm opened this issue Jul 28, 2016 · 2 comments

Comments

@Jorenm
Copy link

Jorenm commented Jul 28, 2016

Serverless Framework Version: 1.0.0-alpha.2
Operating System: Windows 10
Expected Behavior: Deploy the function
Actual Behavior: Errors out
Stack-Trace (Optional):

TypeError: e.message.split is not a function
at module.exports.logError.words.forEach (C:\Users\Ozymandias\AppData\Roaming\npm\node_modules\serverless\lib\classes\Error.js:29:27)
at C:\Users\Ozymandias\AppData\Roaming\npm\node_modules\serverless\bin\serverless:19:15
at tryCatcher (C:\Users\Ozymandias\AppData\Roaming\npm\node_modules\serverless\node_modules\bluebird\js\release\util.js:16:23)
at Promise._settlePromiseFromHandler (C:\Users\Ozymandias\AppData\Roaming\npm\node_modules\serverless\node_modules\bluebird\js\release\promise.js:504:31)
at Promise._settlePromise (C:\Users\Ozymandias\AppData\Roaming\npm\node_modules\serverless\node_modules\bluebird\js\release\promise.js:561:18)
at Promise._settlePromise0 (C:\Users\Ozymandias\AppData\Roaming\npm\node_modules\serverless\node_modules\bluebird\js\release\promise.js:606:10)
at Promise._settlePromises (C:\Users\Ozymandias\AppData\Roaming\npm\node_modules\serverless\node_modules\bluebird\js\release\promise.js:681:18)
at Async._drainQueue (C:\Users\Ozymandias\AppData\Roaming\npm\node_modules\serverless\node_modules\bluebird\js\release\async.js:138:16)
at Async._drainQueues (C:\Users\Ozymandias\AppData\Roaming\npm\node_modules\serverless\node_modules\bluebird\js\release\async.js:148:10)
at Immediate.Async.drainQueues as _onImmediate
at processImmediate as _immediateCallback

@eahefnawy
Copy link
Member

This has been fixed and will be released with Beta 😊

@flomotlik
Copy link
Contributor

@Jorenm in case this isn't fixed with the beta for you please let us know. I'm closing in the meantime

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants