alt Hacker NewsI got OpenClaw to compile Node from source on my old Jetson Nano so that I can run OpenClaw natively instead of using Bun. It took 30 hours but it did it by spinning up a tmux session for the build and using a cron to monitor the tmux pane every hour and even fixing a failure at 5 am which I would have had to find out later had crashed but it had actually found what needed to be changed for the build to continue and it continued building.... Now I have the latest version of OpenClaw running on Node 22 on my 5 year old Jetson Nano running Ubuntu 18 which I cannot upgrade. What they say is all true, it is incredible stuff when it works!
Full story: https://brtkwr.com/posts/2026-03-02-upgrading-openclaw-to-la...
Replies
Apologies if I missed it while skimming your blog post.
But could you estimate the token cost of this? Or were you able to comfortably do this with a subscription plan?
What do you mean "run OpenClaw natively", you're just running Node?
I'm also curious if it's particularly wise to have a web-facing system running on software that hasn't had a security update in 3 years?
That's really cool.
But wouldn't have been quicker and simpler to add ".bun/" to the pattern of authorized paths the same way it presumably works for ".npm/"?