My Glitch logs are not loading for inside the embedded editor.
Here is a working example:
Now, repeat the same actions on the project itself: https://glitch.com/edit/#!/embedded-glitch-project Note that editing the console.log statements there properly triggers a build / log refresh.
A few points of note:
I could not repeat the bug with vanilla Express. Maybe this is related to this particular (pre-release) package? (It wraps Express)
I reviewed the technical restrictions but do not seem to be in violation.
Boosting the app does not solve the issue.
Code changes do, in fact, persist, and the app appears to be updating instantly. The logs / refresh status, however, not.
Any ideas?
1 Like
Its a bit tricky for users without access to the project to replicate this. Could you record a video possibly?
1 Like
Sorry, I thought those were public projects.
Here’s the action shot:
2 Likes
I think you’re missing the part where the project is supposed to listen on port 3000.
Can you show us your package.json?
Thanks @khalby786 . The app currently is listening on port 3000. Should it listen elsewhere?
Here is package.json. Vanilla Glitch Express + one npm package.
The weird thing is the discrepancy with the embedded editor and the stand-alone editor. Shouldn’t these operate identically?
{
"//1": "describes your app and its dependencies",
"//2": "https://docs.npmjs.com/files/package.json",
"//3": "updating this file will download and update your packages",
"name": "hello-express",
"version": "0.0.1",
"description": "A simple Node app built on Express, instantly up and running.",
"main": "server.js",
"scripts": {
"start": "node server.js"
},
"dependencies": {
"express": "^4.17.1",
"mailbots": "^2.0.0"
},
"engines": {
"node": "12.x"
},
"repository": {
"url": "https://glitch.com/edit/#!/hello-express"
},
"license": "MIT",
"keywords": [
"node",
"glitch",
"express"
]
}
Hmmm, looks like a bug. I’d suggest you send an email to support@glitch.com !
1 Like
Thanks. Just pinged them.
1 Like
Embedded glitch projects are a bit different in ways like how you can’t download the entire projects. I think this could be for security so this may be intentional.
1 Like
Maybe, but quietly hiding console.log
output isn’t very friendly. The behavior is also inconsistent – remote editor logs work with some libs and silently fails with others.
1 Like
tasha
November 20, 2020, 6:10pm
10
Thanks for bringing this to our attention! This was a bug on our side that should now be fixed.
If you see this happening again, let us know!
11 Likes
Thank you @tasha ! The fix is confirmed on our end, too
1 Like
system
Closed
May 26, 2021, 4:00pm
13
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.