You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
EDIT: This has been reproduced in Windows by @kiadorii, another friend of ours has confirmed that the repo works properly on Debian.
I hope it's just something minor that I've overlooked, but here is my experience so far:
Clone repo, cd todo to enter this project's root folder
Run npm install; npm run update-schema; npm run build; npm start
Navigate browser to localhost:3000/
See nothing but the contents of public/index.html
I'm trying to follow the path of execution from babel-node ./server.js, and I can't quite understand how the code in js/app.js is reached. Any help would be greatly appreciated, I'm having a very hard time understanding this technology!
Further notes:
The app.js that is generated by webpack is being correctly included in the markup of the final result. This makes me think that the problem is not with webpack, but somewhere in js/app.js.
console.log() statements in app.js do not produce output in the developer console when page is loaded. This makes it seem like the code in app.js is not being executed, despite being included on the page in a script tag.
I'm doing my best to figure this out on my own, but it's all very opaque to me at the moment. Tips for troubleshooting this are just as welcome as the answer to my problem!
The text was updated successfully, but these errors were encountered:
EDIT: This has been reproduced in Windows by @kiadorii, another friend of ours has confirmed that the repo works properly on Debian.
I hope it's just something minor that I've overlooked, but here is my experience so far:
cd todo
to enter this project's root foldernpm install; npm run update-schema; npm run build; npm start
localhost:3000/
public/index.html
I'm trying to follow the path of execution from
babel-node ./server.js
, and I can't quite understand how the code injs/app.js
is reached. Any help would be greatly appreciated, I'm having a very hard time understanding this technology!Further notes:
app.js
that is generated by webpack is being correctly included in the markup of the final result. This makes me think that the problem is not with webpack, but somewhere injs/app.js
.console.log()
statements inapp.js
do not produce output in the developer console when page is loaded. This makes it seem like the code inapp.js
is not being executed, despite being included on the page in a script tag.I'm doing my best to figure this out on my own, but it's all very opaque to me at the moment. Tips for troubleshooting this are just as welcome as the answer to my problem!
The text was updated successfully, but these errors were encountered: