I made a portfolio website, but this site doesn't stop loading.
Sorce code is here.
Does anyone have a solution? or the reason why this happens?
Deploy only your bundled static files. I can access your entire svelte project under your domain. check the sources tab in your browser's DevTools.
since you use vercel for deployment, check this out.
https://github.com/vercel/serve
Check for service workers (If you are using them)
But more probably
2) ALWAYS npm run build before firebase deploy
Related
I created a simple app built using React and a Rest api. It deployed successfully using Heroku, but when the app is opened it only displays the header. In addition, it displays the header as a full page; nothing else appears. When I run "npm start" to view the app in the IDE/browser, it is perfect. It is only when deployed that it fails to display the entire app.
Resolved: I was able to resolve the issue. Hopefully, someone will benefit from what I have learned. When deploying to Heroku, make sure that you are deploying from the local main branch and not a feature branch. Cross-branch actions are not permitted with Heroku.
I have the next error: "Deceptive site ahead". My app is separate in frontend with Angular 8 and backend with Laravel 5.8. The issue is when I deploy the backend to a subdomain (services), Google Chrome shows me that error. What's wrong?
I've done the same with another easy Laravel project and it's fine, but I don't know why it happens in this project.
I hope someone helps me and sorry for my English.
Nothing to do with your code. Google has blacklisted/marked as unsafe your site for some reason which can harm users. If it is not done by you then you may have some script or file on your server which google has found and thinks it is unsafe. After clearing your files you may try to submit for review.
Check here more detailed information: https://www.malcare.com/blog/deceptive-site-ahead/
My portfolio is made on Gatsby and deployed to Netlify. It works fine locally but there are bugs on the live site on Netlify. How can I debug this? I cannot use console.log and there are no console errors. How can I debug this?
The issues are to do with a component that shows based on whether a hook is true and the image doesn't render through childImageSharp
If it's being hosted on Netlify, all it is doing is running gastby build and then serving the site up from the public folder. You should be able to run gatsby build && gatsby serve locally to mimic the issue you're seeing on your deployed site. If you can't reproduce it, try cleaning out your .cache and public folders with gatsby clean.
I have an Ubuntu VPS with Laravel v5.6 served with nginx, and I am trying to use React on the front-end. I don't know if this is possible what I want to do is:
use node and npm to build my front-end app locally,
generate the CSS and JS files and upload those already generated files to my VPS server,
the output should not change since as far as I know npm generates at JS and CSS files with your whole code in it
Thanks for the help, and if there is any suggestion for a different approach just let me know.
You should start to use a frontend bundling solution like webpack or parcel, they do exactly the same
If you generate your app with create-react-app it comes with webpack built-in
Problem: Pakyow App deployed to Heroku and all JS and CSS sourced/linked in template head 404.
I assume this is a problem stemming from Heroku, but rather not one that I am aware of. As far as I know, Heroku allows static assets in the public directory.
Anyway, looking for some helpful pointers from Pakyow users.
The app (currently) is at http://pakyow-go.herokuapp.com and the repo can be found at http://github.com/jphager2/pakyow-go.
This is an unfortunate default config option in the currently released version. To get around it, add this to the production configuration block in app.rb:
app.static = true
The reason it works this way out of the box is in most production cases you don't want the app serving static files. This would instead be the responsibility of the HTTP server. On Heroku though, you want the app server to serve static files unless you host them from a CDN.