Happy May everyone! We’ve got a few updates to share with what’s new on Glitch across content, preview and platform. Check it out:
A big leap forward for the new Glitch, you can start to personalize your profile.@allypalanzi deployed another update to preview.glitch.com so you can now pin and feature projects. Try it out, let us know any bugs in this thread, and let us know your thoughts on the preview so far. One thing we’ve been talking about is moving away from iframes and more towards project screenshots - what are your thoughts?
This week we’re testing a small number of containers that have the default Node version set to 12 (right now the default is 10). Given how that test goes, we’ll likely set a maintenance window for Thursday (tomorrow, which I’ll post a separate thread about that today) to apply changes across all projects. This should only impact projects without “engines” set in package.json, but it could have some other unpredictable effects on containers which is why we’ve been treading as carefully as we’ve been. After this is done, we can go all in on the work that we’ve already been doing in parallel to get the container OS updated and get more recent versions of Node available. We appreciate your patience as we work on all of this!
I’m working on putting together the next community test that should be going out next month, so expect some calls to join our testing group if you’ve not already. One of the tests is to try out recent Node versions on containers, and another one is a surprise but here’s a hint: it’s an exciting new functionality we’re adding to user profiles in the glitch preview. If you guess what it is correctly, I will mail you a bunch of Glitch and Fastly stickers.
hey, sorry this is happening! please try deleting your cookies & local storage for the preview.glitch.com subdomain and see if you can log in fresh. We’re still working out some of the intricacies of how we authorize requests to our API, and we’ll definitely get those bugs fixed and also improve the error messages over the coming months.
hi, are there any updates on the node upgrade? just wanted to know because a lot of frontend frameworks have moved onto Node 18 as the base requirement which makes it a bit tough to start a new Vue/Astro/Next.js project on Glitch!
the only alternative is to use earlier versions of these frameworks, most of which have outdated tooling and have become EOL
No update right now. Because of the holiday yesterday, we have a lot of folks out taking a much needed break and so when everyone’s back I’ll work to get a fresh update out on here.