Closed fengcj closed 7 years ago
This is because you have a malformed JWT in your local storage. If you remove that it'll work fine.
We should probably fix the app so it removes it for you in that case. Would you like to do that? 😀
@kentcdodds , thanks for quick reply. How can I remove my malformed JWT?
Sorry, I'm on mobile, but Google how to access local storage for your browser in the dev tools.
if you mean remove malformed JWT is clear local storage in the browser, I had done that, but still not working. @kentcdodds , please feel free to do you own job first. I can wait when you have the time to solve this issue. Thank you again.
I believe I've resolved the issue. You should be able to just do a git pull and get the updated (working hopefully?) app 👍
@kentcdodds , now it works as expected. great job!
@kentcdodds so far I'm loving the course! I just pulled down master and went through the setup. When I run yarn start dev
my app is also loading without any articles or tags. In the dev tools there is nothing in Application > Local Storage to remove and I'm not seeing any errors...I'm running –
Any idea what might be going on?
Could be that your load-database
script failed. Try this:
node ./scripts/load-database
The problem was I was trying to run this from my Dropbox folder. Once I moved it over to a different directory everything built perfectly. Thanks for the assistance @kentcdodds!
Ah, yeah, putting npm-based projects in dropbox is probably not advisable considering how HUGE the node_modules directory can be 😅
Glad you got it working!
Environment info:
mongo
version (mongod --version
): v3.0.3node
version (node --version
): v7.6.0npm
version (npm --version
): 4.1.2yarn
version (yarn --version
): 0.22.0Problem description:
1) run
npm start dev
without any error 2) launchhttp://localhost:8080/#/
successfully, but the content of the website is as below:https://github.com/fengcj/weewikipaint/blob/master/screen.png
3) check the response of
/api/articles?limit=10&offset=0
as below: {"articles":[],"articlesCount":0}I guess this might be the DB issue.
@kentcdodds , please give me some suggestion.