Skip to content

Missing bundles / parse-dashboard not working #545

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

Closed
mohannad-abwah opened this issue Sep 28, 2016 · 3 comments
Closed

Missing bundles / parse-dashboard not working #545

mohannad-abwah opened this issue Sep 28, 2016 · 3 comments
Labels
state:wont-fix Won’t be fixed with a clearly stated reason

Comments

@mohannad-abwah
Copy link

mohannad-abwah commented Sep 28, 2016

I've been trying to get parse-dashboard running on Azure for a few days now with no luck. I get an empty white page. After looking into it a little bit more it seems it's not set up correctly as the entire bundles folder is missing in wwwroot/Parse-Dashboard/public.

Environment Setup / repro steps

  1. Go to Azure portal
  2. Deploy a new web app
  3. Go to Deployment options
  4. Hook it up to this repo directly using external repository
  5. Add the following environment variables in Application Settings:
    PARSE_DASHBOARD_ALLOW_INSECURE_HTTP: 1
    PARSE_DASHBOARD_SERVER_URL:
    PARSE_DASHBOARD_MASTER_KEY:
    PARSE_DASHBOARD_APP_ID:
    PARSE_DASHBOARD_APP_NAME:
    PARSE_DASHBOARD_USER_ID: "user1"
    PARSE_DASHBOARD_USER_PASSWORD: "pass"
  6. Restart

Try it here: http://brokenparsetest.azurewebsites.net/
(don't worry that's just a test server with no important information whatsoever)

Logs/Trace

It says deployment went fine. In fact even the request for the dashboard.bundle.js returns a 200, but since the file doesn't exist the content doesn't make any sense. It's actually identical to the HTML that comes back, which doesn't work.

If I go into the App Service Editor and run "npm run dev" in the console manually I get this:

\> npm run dev

> [email protected] dev D:\home\site\wwwroot
> node ./Parse-Dashboard/index.js & webpack --config webpack/build.config.js --devtool eval-source-map --progress --watch


D:\home\site\wwwroot\Parse-Dashboard\index.js:10
const path = require('path');
^^^^^
SyntaxError: Use of const in strict mode.
    at Module._compile (module.js:439:25)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Function.Module.runMain (module.js:497:10)
    at startup (node.js:119:16)
    at node.js:906:3
'webpack' is not recognized as an internal or external command,
operable program or batch file.

npm ERR! Windows_NT 6.2.9200
npm ERR! argv "D:\\Program Files (x86)\\nodejs\\0.10.29\\node.exe" "D:\\Program Files (x86)\\npm\\3.9.5\\node_modules\\npm\\bin\\npm-cli.js" "run" "dev"
npm ERR! node v0.10.29
npm ERR! npm  v3.9.5
npm ERR! code ELIFECYCLE
npm ERR! [email protected] dev: `node ./Parse-Dashboard/index.js & webpack --config webpack/build.config.js --devtool eval-source-map --progress --watch`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] dev script 'node ./Parse-Dashboard/index.js & webpack --config webpack/build.config.js --devtool eval-source-map --progress --watch'.
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 parse-dashboard package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node ./Parse-Dashboard/index.js & webpack --config webpack/build.config.js --devtool eval-source-map --progress --watch
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs parse-dashboard
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls parse-dashboard
npm ERR! There is likely additional logging output above.
@nyxee
Copy link

nyxee commented Sep 12, 2017

please people, is there no way of hacking this?
I see no complaints n this issue for 2017.
did people give up on Parse?

@flovilmart
Copy link
Contributor

'webpack' is not recognized as an internal or external command,
operable program or batch file.

Seems that either web pack is not installed, npm install hasn't been run or else...

@stale
Copy link

stale bot commented Jan 10, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:wont-fix Won’t be fixed with a clearly stated reason
Projects
None yet
Development

No branches or pull requests

3 participants