-
Notifications
You must be signed in to change notification settings - Fork 95
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
[QUESTION] Deployment issue #58
Comments
From the error message, it seems NodeJS tried to run ES6 without babel. To run server side code without pre-built with babel (like in development), we should point the entry file to Or, there's a task inside |
Thanks that was one of the problems 👍 Theres some more issues when deploying on Azure, managed to solve them all now im improving procedure a bit. I'll write steps needed in case someone else tries to do the same. Thanks |
For deployment on Azure Web App:
More info about this can be found: |
Hi,
We are currently trying to deploy this boilerplate on Windows Azure AppService. Thats basically NodeJs server wrapped into iisnode module(in essence it should function the same as nodejs/express server).
When using steps for deployment, locally it works fine. However, when deployed on Azure app service we are getting the following error:
(function (exports, require, module, __filename, __dirname) { import Express from 'express' ^^^^^^ SyntaxError: Unexpected token import at Object.exports.runInThisContext (vm.js:76:16) at Module._compile (module.js:542:28) at Object.Module._extensions..js (module.js:579:10)
For Azure deployment all that needs to be done is to configure web.config file which points to server.js file which should not be the cause of this issue. It seems that this is something to do with babel transpiler missing on deployment machine.
Any idea on how to solve this issue?
Thank you
The text was updated successfully, but these errors were encountered: