-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Running mozilla hubs build on AWS Cloud 9 #410
Comments
Hi Jeff. It's not entirely clear what's going wrong, but I would start by upgrading nodejs, you'll need v8 or v9 |
Here is the latest after the node update to 8 as suggested. Could installing with npm install and npm run start rather than yarn install, yarn build be causing this issue? `ec2-user:~/environment/hubs/src (master) $ npm run start
(node:3955) DeprecationWarning: Tapable.plugin is deprecated. Use new API on ERROR in ./src/assets/stylesheets/index.scss (./node_modules/css-loader??ref--6-2!./node_modules/sass-loader/lib/loader.js!./src/assets/stylesheets/index.scss) ERROR in ./src/assets/stylesheets/hub.scss (./node_modules/css-loader??ref--6-2!./node_modules/sass-loader/lib/loader.js!./src/assets/stylesheets/hub.scss) ERROR in ./src/assets/stylesheets/link.scss (./node_modules/css-loader??ref--6-2!./node_modules/sass-loader/lib/loader.js!./src/assets/stylesheets/link.scss) ERROR in ./src/assets/stylesheets/link-dialog.scss (./node_modules/css-loader??ref--6-2!./node_modules/sass-loader/lib/loader.js!./src/assets/stylesheets/link-dialog.scss) ERROR in ./src/assets/stylesheets/footer.scss (./node_modules/css-loader??ref--6-2!./node_modules/sass-loader/lib/loader.js!./src/assets/stylesheets/footer.scss) ERROR in ./src/assets/stylesheets/2d-hud.scss (./node_modules/css-loader??ref--6-2!./node_modules/sass-loader/lib/loader.js!./src/assets/stylesheets/2d-hud.scss) ERROR in ./src/assets/stylesheets/avatar-selector.scss (./node_modules/css-loader??ref--6-2!./node_modules/sass-loader/lib/loader.js!./src/assets/stylesheets/avatar-selector.scss) |
Case closed. I was unfamiliar with Yarn, installed it with updated node and it successfully compiled. |
Glad to hear it. Let us know if you run into other issues. |
I'm running into an issue viewing the application running in the browser. In AWS cloud 9, it shows that the app is successfully built and gives an address on port 8080. When opening link in a browser, it times out after a min. and doesn't load. I'm on a mac and have tried opening the link on safari, chrome, and firefox. What else do I need to do to get it working? It shows also shows everything running on its EC2 instance, so i'm sure its related to browser permissions. Do I need to open another ticket? |
Hello,
After doing the install to AWS Cloud 9, the errors below pop up in the console. What might be the solution to these errors? thanks in advance.
npm ERR! Linux 4.14.33-51.37.amzn1.x86_64
npm ERR! argv "/home/ec2-user/.nvm/versions/node/v6.14.2/bin/node" "/home/ec2-user/.nvm/versions/node/v6.14.2/bin/npm" "run" "start"
npm ERR! node v6.14.2
npm ERR! npm v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! [email protected] start:
cross-env NODE_ENV=development webpack-dev-server
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script 'cross-env NODE_ENV=development webpack-dev-server'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the mr-social-client package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! cross-env NODE_ENV=development webpack-dev-server
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs mr-social-client
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls mr-social-client
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /home/ec2-user/environment/hubs/npm-debug.log
The text was updated successfully, but these errors were encountered: