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

Service Controller not rendering #4506

Closed
vishu9219 opened this issue May 23, 2018 · 1 comment
Closed

Service Controller not rendering #4506

vishu9219 opened this issue May 23, 2018 · 1 comment

Comments

@vishu9219
Copy link

vishu9219 commented May 23, 2018

Is this a bug report?

Yes

Did you try recovering your dependencies?

Yes, no issue with dependency.

Package.json
{
"name": "public",
"version": "0.1.0",
"private": true,
"homepage": "./",
"dependencies": {
"bootstrap": "^3.3.7",
"lodash": "^4.17.5",
"prop-types": "^15.6.1",
"react": "^16.3.2",
"react-dom": "^16.3.2",
"react-render-html": "^0.6.0",
"react-router-dom": "^4.2.2",
"react-scripts": "1.1.4",
"reactstrap": "^5.0.0-beta.3"
},
"scripts": {
"start": "react-scripts start",
"build": "react-scripts build",
"test": "jest",
"eject": "react-scripts eject"
},
"devDependencies": {
"babel-jest": "^22.4.3",
"babel-preset-env": "^1.6.1",
"babel-preset-react": "^6.24.1",
"jest": "^22.4.3",
"react-test-renderer": "^16.3.2"
}
}

12:22:10 › npm --version
5.6.0

Environment

Development

Steps to Reproduce

  1. You launch react application
  2. Let's say react is running on localhost:3000
  3. Setup a proxy server which takes the request on localhost:4000.
  4. All the request coming from localhost:4000/xyzabc should redirect to localhost:3000

Expected Behavior

Whatever coming on localhost:3000 should come on localhost:4000/xyzabc

Actual Behavior

JS CSS everything is getting downloaded but nothing is showing on UI. UI is totally blank
screen shot 2018-05-23 at 12 34 35

Reproducible Demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

@Timer
Copy link
Contributor

Timer commented May 24, 2018

Closing as a duplicate of #4468, this is a known issue. Sorry!
It should be fixed in v2.

@Timer Timer closed this as completed May 24, 2018
@lock lock bot locked and limited conversation to collaborators Jan 19, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants