We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I didn't find any manuals and errors I've implemented it on my server with the sudo npm run-script build
sudo npm run-script build
I have set my package json
{ "name": "shards-dashboard-lite-react", "version": "1.0.0", "private": true, "homepage": "http://xx.xx.xx.xx/apps/spk/", "dependencies": { ................................... ..............................
i have try to with "homepage": "./",
"homepage": "./",
still blank page and no error .
but when I try to implement with netfliy, it's ok (no problem, no error)
i have try with other project react without template (defaut react) build and deploy to my server ,it's ok (no problem, no error)
http://47.254.248.35/apps/spk/ // shard dashboard http://47.254.248.35/apps/books/ // default
thanks in advance
The text was updated successfully, but these errors were encountered:
I facing the same issue. after uploading all files from a yarn build , there is a blank page.
yarn build
Sorry, something went wrong.
I have solved by using MemoryRouter instead of BrowserRouter @Nsengiyunva
No branches or pull requests
I didn't find any manuals and errors
I've implemented it on my server with the
sudo npm run-script build
I have set my package json
i have try to with
"homepage": "./",
still blank page and no error .
but when I try to implement with netfliy, it's ok (no problem, no error)
i have try with other project react without template (defaut react) build and deploy to my server ,it's ok (no problem, no error)
http://47.254.248.35/apps/spk/ // shard dashboard
http://47.254.248.35/apps/books/ // default
thanks in advance
The text was updated successfully, but these errors were encountered: