Today we’re announcing our next phase in building a whole new Glitch and it’s one that’s directly tied to what a lot of you have been waiting for: updated versions of Node on containers.
Projects running on those versions will not wake up on those deprecation dates and those versions will not be available on containers, you’ll need to go into the editor and update them.
I’m bumping this thread so folks know that tomorrow (12/1) is the date we are deprecating Node 6. If you run into any issues, let us know here or you can file a ticket at https://help.glitch.com.
Hello - there are a number of “featured” glitch projects that seem to be affected by this node update such as many here https://glitch.com/@glitch/building-blocks. This is a shame because not only do they not work, it seems you also can’t have a look a the code! (View Source doesn’t work either)
My question is, given it is not practical to expect all creators to update node, can anyone suggest some sort of workaround to view the code - eg an autolink to a github repository or some sort of “read only” mode? Particularly on the projects which are part of an officially curated list. Seems a shame if they are gone forever.
I know it’s not a great experience, but you can remix any of those projects since they’re public (there’s a “remix your own” button below the embed on the project page of any public project) and have your own copy that you can update the version of Node to keep running! If you’re the owner of a project with an out of date version of Node you can still see the code in the editor and update it.
