1/ Super-excited to release the first complete rewrite to the Pyret home page in 10 years, corresponding to major language improvements! So many cool new things, let me give you a brief tour: ↵ pyret.org
Replies
2/ First of all, the page is full of executable examples embedded in the page. There are several small examples; clicking on "Run it!" will show you bigger versions. There's a very fun example at the top right; give it a try! ↵
aug 29, 2025, 3:28 pm • 1 0 • view
3/ Pyret is actually a pretty large, full-featured language. There's now a "Major Features" button that gives you a pop-up listing most of them. Again, every single one has carefully-chosen executable examples! ↵
aug 29, 2025, 3:28 pm • 2 0 • view
4/ Pyret has always had a sorta-kinda-supported VSCode extension. Now it's official! You can find it linked from the home page. You can also use github . dev as your running platform. ↵
aug 29, 2025, 3:28 pm • 2 0 • view
5/ The npm package has been significantly improved! So you can run Pyret on your command line if you really want to (or need to, e.g., for autograding). ↵
aug 29, 2025, 3:28 pm • 0 0 • view
6/ If you're wondering "does this mean there's now support for the local filesystem?", we're glad you asked! Yes, there is. We're starting to really support working offline, not on GDrive, etc. to handle various privacy concerns. ↵
aug 29, 2025, 3:28 pm • 0 0 • view
7/ The DCIC book is also starting to take advantage of these changes. Only slightly so far, but it will grow now that these things are official. This creates so many more options and possibilities for us. ↵ dcic-world.org
aug 29, 2025, 3:28 pm • 4 1 • view
8/ There's even more! Please see the new home page, and also read our release notes for even more details. Also see the Scuttlebutt link on the home page to get in touch with us! ↵ pyret.org/release-note...
aug 29, 2025, 3:28 pm • 2 0 • view
Installed the npm package (on macos). The "ahoy" example in the cmdline docs (`pyret --help`) gives the error in the picture. The VSCode extension works though.
aug 31, 2025, 12:52 am • 1 0 • view
CC @joepolitz.bsky.social
aug 31, 2025, 1:38 am • 0 0 • view
Oh my, thanks for showing us this. I can't reproduce this (I do know of some install issues related to node versions, but they don't look like this). If you're up for sharing more, it would help me to see the output of pyret --version node --version and any warnings you got from the install step
sep 2, 2025, 3:40 pm • 1 0 • view
fwiw ... pyret --version gives v0.0.64 node --version gives v24.2.0
sep 2, 2025, 4:31 pm • 1 0 • view
Useful, I'll see if it's a npm vs yarn thing with how modules are getting resolved. One more piece of information if you can share – from the directory where you got the error about not finding `resolve` when running the pyret command: ls -la ls -la .pyret
sep 2, 2025, 5:26 pm • 0 0 • view