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
We load custom/custom.js using require along with all of our own modules, and page.show() is called in the success callback for that require call. So if there's a 404 on custom.js, you're left with a blank page, and only a message at the JS console says what the problem is.
We should load custom.js separately, since it doesn't matter if it's not there.
It would also be good to have something more informative than a blank page if something fails to load, but that's not the focus of this issue.
The text was updated successfully, but these errors were encountered:
I can't seem to make it 404. Did you restart your nbserver? #16 changed the URL for custom from /static/custom to /custom since it's handled specially. What do you see at http://localhost:8888/custom/custom.js?
We load
custom/custom.js
using require along with all of our own modules, andpage.show()
is called in the success callback for that require call. So if there's a 404 on custom.js, you're left with a blank page, and only a message at the JS console says what the problem is.We should load custom.js separately, since it doesn't matter if it's not there.
It would also be good to have something more informative than a blank page if something fails to load, but that's not the focus of this issue.
The text was updated successfully, but these errors were encountered: