![Cover image for Best Resources For Web Developers 💻 [HTML + CSS + JavaScript]](https://media.dev.to/cdn-cgi/image/width=1000,height=420,fit=cover,gravity=auto,format=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F6ytzuvklqr5edicelhqr.jpg)
Here is a list of 24 valuable resources for web developers, covering HTML, CSS, and JavaScript.
Keep in mind that there may be newer res...
For further actions, you may consider blocking this person and/or reporting abuse
wow, what an explosion of relevant content, I knew some, but some were great finds, thank you very much for creating an article with links and a brief explanation, thank you very much for sharing your knowledge 🦤.
my pleasure :)
I'd love to recommend my newsletter too, Unicorn Club 🦄
5-minute bite-sized weekly newsletter for design-savvy front-end devs and code-loving UX/UI designers. Filled with the best hand-picked resources. 100% free.
Subscribe for free
I will surely check it! :)
Hello, I'm fresher and I had created a dynamic react app with ms sql in that I'm facing issue as after production build it's looks good but after refreshing or reloading the same page getting error as 'can't get /login' can suggest some solution Thank you!
It seems like you're facing an issue with routing in your React app, particularly when reloading the page. The error message "can't get /login" suggests that the server is unable to find a route for the "/login" path.
Here are a few steps you can take to troubleshoot and potentially resolve the issue:
Check Your Server Configuration:
Ensure that your server (backend) is correctly configured to handle routing and is set up to serve the React app correctly. Make sure that it can handle routes like "/login" and that it's not expecting a physical file at that location.
Use HashRouter instead of BrowserRouter:
If you are using
BrowserRouter
fromreact-router-dom
, try switching toHashRouter
.HashRouter
uses the hash portion of the URL (e.g.,http://example.com/#/login
) to maintain the application state. This can help with page reloads, as the part after the hash is typically handled client-side.Set up Proper Routing on the Server:
Ensure that your server is configured to serve the same
index.html
file for any route. This is known as a catch-all or wildcard route. In many server frameworks, you can achieve this by configuring your server to always return theindex.html
file for any route. This ensures that the React app takes over routing on the client-side.Check Your
package.json
forhomepage
Configuration:If you have set the
"homepage"
field in yourpackage.json
, make sure it is correctly set, especially if your app is not deployed at the root of the domain.Check for Typos and Case Sensitivity:
Ensure that the paths specified in your React Router components match the paths expected by the server, and that they are correctly spelled and cased.
After making these checks, you should be able to identify and resolve the issue. If the problem persists, you may need to provide more details about your project structure, server setup, and routing configuration for further assistance.
You may add cssgridgarden.com/ - the CSS Grid game counterpart of Flexbox Froggy :)
Thanks for the info !! :)
very helpful, thnx
my pleasure! :)
Great post, I have this bookmarked now in case if I need it!
Glad to hear that!
I love posts like this. Thanks, I'll definitely use it.
Good to hear that !!! :)
Thanks! Very useful for a noob like me :P
my pleasure :)
This is helpful, thank you
my pleasure :)
Great list!
Thanks !!
Wonderful list 🔥🔥
Thanks !!!
Yeah, thats true.
MDN web docs are quite handy for js! And w3schools is a good one for starting the journey.